Skip to content
Snippets Groups Projects
  1. Jul 29, 2004
    • rtoy's avatar
      (defun foo () (zot)) when compiled and run gave a silly message about · 7d79b30c
      rtoy authored
      #C(0d0 0d0) failing a typecase.  Then doing a backtrace gave another
      error about some negative number not being a positive fixnum.
      
      The former error is caused by a bad definition of undefined_tramp.
      The latter error is caused by the debugger not being able to compute
      the offset correctly.
      
      (Fixes ported from sbcl.)
      7d79b30c
  2. Jun 01, 2004
  3. Apr 01, 2004
    • rtoy's avatar
      From Helmut Eller: · 0519cdf6
      rtoy authored
      parse-compiled-debug-function-lambda-list fails for
      
        (di::debug-function-lambda-list
          (di::function-debug-function
            #'pcl::fix-early-generic-functions))
      
      because it tries to nconc the supplied-p var to a deleted keyword arg.
      0519cdf6
  4. Nov 25, 2003
  5. Nov 21, 2003
  6. Aug 24, 2003
    • gerd's avatar
      Debugger signalling an error when a function parameter is · b8e7cf93
      gerd authored
      	a special variable.  Reported by Alexey Dejneka on cmucl-imp.
      	This fixes the read case, but not the setq case.
      
      	* src/code/debug-int.lisp (preprocess-for-eval): Don't
      	symbol-macrolet special variables, let-bind them instead.
      b8e7cf93
  7. Jul 21, 2003
    • gerd's avatar
      * src/code/ntrace.lisp (trace-1): Encapsulate if · ed92e5cc
      gerd authored
      	can-set-function-end-breakpoint-p returns false.
      
      	* src/code/debug-int.lisp (can-set-function-end-breakpoint-p):
      	Return true of compiled-debug-function-returns is :standard.
      ed92e5cc
  8. May 11, 2003
  9. Apr 24, 2003
  10. Aug 27, 2002
    • moore's avatar
      · bf84be07
      moore authored
      On x86 FreeBSD and Linux, change the way foreign symbol addresses are resolved.
      They now go through a table -- effectively a new space in the core file.
      Function references are resolved lazily, data references are resolved on startup
      and when a .so is loaded.  The end result is that cores can be dumped that
      contain references to symbols in shared libraries.  Also, the dependence of the core on addresses in the Lisp runtime is broken.
      
      The linkage table feature is controlled by :linkage-table and LINKAGE_TABLE in C
      runtime.  Several foreign symbols are now Lisp static symbols, so a cross
      compile is required whether or not the new stuff is used.  I've checked in
      boot4-cross-foreign-linkage.lisp that builds the compiler for linkage table; do whatever you usually do for the non-linkage table case:)  Seriously, lets start
      a discussion on standardizing "cross compilation," not to mention the general
      build procedure.
      bf84be07
  11. Mar 04, 2001
  12. Nov 15, 2000
  13. Nov 06, 2000
  14. Sep 17, 1999
  15. Aug 28, 1999
  16. Aug 03, 1999
  17. Aug 14, 1998
  18. Jul 24, 1998
  19. Apr 10, 1998
  20. Mar 21, 1998
  21. Feb 14, 1998
  22. Jan 25, 1998
  23. Jan 19, 1998
  24. Jan 16, 1998
  25. Dec 30, 1997
  26. Dec 15, 1997
  27. Dec 07, 1997
  28. Dec 05, 1997
  29. Dec 03, 1997
  30. Nov 29, 1997
  31. Nov 25, 1997
    • dtc's avatar
      Re-write of the x86 port debug support. This should give a significant · fa77470b
      dtc authored
      improvement in reliability necessary for breakpoint and single
      stepping to have a chance, and has been tested in the experimental
      code and works on FreeBSD and Linux.
      
      The code object for a given return address in now located with the help
      of the GC support function component_ptr_from_pc which can reliably
      locate the code objects. This uses a forward search of the heap so is
      rather slow - some caching will be needed for better performance.
      
      The stack parsing has been re-written using a backtracking search to
      improve the chance of finding a valid frame path given that the
      control changes between C and Lisp conventions.  The x86-lra hack is
      no longer necessary (was unreliable anyway) allowing x86 code to be
      more compact. The return address is now handled as a SAP which is
      acceptable because the code doesn't move with CGC, and GENCGC ensures
      that code objects in the dynamic heap with return addresses on the
      stack are not moved. However there are known problems under GENCGC
      when return addresses are move off the stack during some breakpoint
      operations in which case the code object may move.
      fa77470b
  32. Nov 18, 1997
  33. Nov 15, 1997
  34. Nov 07, 1997
  35. Nov 04, 1997
    • dtc's avatar
      Add a check that objects obtained from the stack in · 54c1961a
      dtc authored
      sub-access-debug-var-slot (x86) are valid.  Debug variable locations
      are not always valid, and on the x86 there can be non-descriptor
      objects on the stack.
      
      Cleanup the sap-ref code in sub-access-debug-var-slot and
      sub-set-debug-var-slot which had been using convoluted code to work
      around sap-ref bugs that have since been fixed.
      54c1961a
    • dtc's avatar
      Merge in changes to the x86 backend from the gencgc branch, allowing · 725ab9ee
      dtc authored
      common binaries to be run on both:
      
      * The immediate-stack storage class has been removed, this is
      unnecessary as the descriptor-stack SC can be used. It may have once
      been part of some GC stragety to reduce the number of stack slots that
      needed to be noted for a GC.
      
      * The object allocation has been abstracted and cleaned up. This
      should produce slightly faster smaller code with CGC, and can be
      compiled to support inline allocation with GENCGC.  CGC compiled code
      will run under GENCGC, and GENCGC binaries that don't use inline
      allocation will run under CGC.
      
      * A random hash is now placed in the unused symbol object slot (the
      symbol-hash slot). This saves flushing the info cache at each GC, and
      may have other uses for symbol based hash tables. Should help MP
      safety.
      
      * Common set of static symbols used by both CGC and GENCGC.
      
      * Corrections to the stack-ref VOP; now returns lisp objects not
      unsigned numbers. Required some patches to debug-int.
      
      * Inline unsigned/signed byte 32 to bignum allocation enabled.
      
      * Support for the x86 xadd instruction applied to instance slot and
      symbol values - may be handy for some MP code.
      
      * Bump up the FASL file version from 1 to 2.
      725ab9ee
  36. Feb 08, 1997
    • pw's avatar
      From: Douglas Thomas Crosher <dtc@scrooge.ee.swin.oz.au> · 0efcc964
      pw authored
      Message-Id: <199702041630.DAA06602@scrooge.ee.swin.oz.au>
      Subject: Re: making eval-functions FINs
      To: cmucl-imp@cons.org
      Date: Wed, 5 Feb 1997 03:30:55 +1100 (EST)
      In-Reply-To: <199702040300.EAA16744@knight.cons.org> from "Rob MacLachlan" at Feb 3, 97 09:59:02 pm
      X-Mailer: ELM [version 2.4 PL24]
      Content-Type: text
      
      
      > I seem to have lost the most recent message about fixing compiler/eval to
      > use FINs instead of closures.  But yes, I would think that the current
      > EVAL-FUNCTION  slots should become slots in the interpreted function FIN.
      > GET-EVAL-FUN when would then become IDENTITY, so it should probably be
      > flushed entirely.
      
      Done; moved eval-function data into the interpreted-function FIN, also
      added a closure slot so describe can access it easily. Revised patches
      below.
      
      Douglas
      0efcc964
Loading