Skip to content
Snippets Groups Projects
  1. Nov 16, 2004
    • cwang's avatar
      typo · e40848aa
      cwang authored
      e40848aa
  2. Oct 13, 2004
  3. Aug 30, 2004
  4. Aug 03, 2004
  5. Jul 30, 2004
  6. 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
  7. Jun 01, 2004
  8. 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
  9. Nov 25, 2003
  10. Nov 21, 2003
  11. 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
  12. 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
  13. May 11, 2003
  14. Apr 24, 2003
  15. 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
  16. Mar 04, 2001
  17. Nov 15, 2000
  18. Nov 06, 2000
  19. Sep 17, 1999
  20. Aug 28, 1999
  21. Aug 03, 1999
  22. Aug 14, 1998
  23. Jul 24, 1998
  24. Apr 10, 1998
  25. Mar 21, 1998
  26. Feb 14, 1998
  27. Jan 25, 1998
  28. Jan 19, 1998
  29. Jan 16, 1998
  30. Dec 30, 1997
  31. Dec 15, 1997
  32. Dec 07, 1997
  33. Dec 05, 1997
  34. Dec 03, 1997
  35. Nov 29, 1997
  36. 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
Loading