Skip to content
Snippets Groups Projects
  1. Jun 30, 2006
  2. Jan 23, 2006
    • rtoy's avatar
      Implement tracing of flet/labels functions. This probably needs more · 45d04c07
      rtoy authored
      work and could probably be implemented better.
      
      With these changes (trace (labels foo bar)) will trace the labels
      function FOO in the function BAR.  We only support encapsulate nil,
      here.  No check is made for this.
      
      code/ntrace.lisp:
      o In TRACE-FDEFINITION, recognize a list as a valid function, and
        return the list as the value of TRACE-FDEFINITION.  This seems
        wrong, but I'm not sure if there's a real fdefinition for it, or if
        we could create a fake one.
      
      code/debug-int.lisp:
      o In FUNCTION-DEBUG-FUNCTION, recognize a list as the name of a
        function, and find the corresponding compiled-debug-function and
        create and return the new compiled-debug-function.
      45d04c07
  3. Mar 18, 2005
  4. Mar 17, 2005
    • rtoy's avatar
      Implement tracing for the known-return convention. This is basically · 46a81e81
      rtoy authored
      Helmut Eller's patch sent to cmucl-imp on 2005-03-08.  This basically
      means tracing recursive functions will show all recursions during the
      trace and not just the final call.
      
      code/debug-int.lisp:
      o Apply Helmut's patch.  Tweak it so when the known-return convention
        is being used, we tell MAKE-BOGUS-LRA that we're using the
        known-return so we can handle it properly.
      
      lisp/breakpoint.c:
      o Add an extra parameter to compute_offset so we know we're handling a
        function-end breakpoint or not.  Needed because reg_CODE isn't
        pointing to the bogus lra in this case, so the offsets are all
        wrong.  We compute the right offset for the known return and return
        the offset as negative so we can tell.
      o Adjust all callers of compute_offset.
      o Adjust handle_function_end_breakpoint to handle negative offsets
        from compute_offset so we can get the right code component for the
        bogus lra.
      46a81e81
  5. Nov 20, 2004
  6. Nov 19, 2004
  7. Nov 17, 2004
  8. Nov 16, 2004
    • cwang's avatar
      typo · e40848aa
      cwang authored
      e40848aa
  9. Oct 13, 2004
  10. Aug 30, 2004
  11. Aug 03, 2004
  12. Jul 30, 2004
  13. 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
  14. Jun 01, 2004
  15. 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
  16. Nov 25, 2003
  17. Nov 21, 2003
  18. 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
  19. 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
  20. May 11, 2003
  21. Apr 24, 2003
  22. 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
  23. Mar 04, 2001
  24. Nov 15, 2000
  25. Nov 06, 2000
  26. Sep 17, 1999
  27. Aug 28, 1999
  28. Aug 03, 1999
  29. Aug 14, 1998
  30. Jul 24, 1998
  31. Apr 10, 1998
  32. Mar 21, 1998
  33. Feb 14, 1998
  34. Jan 25, 1998
  35. Jan 19, 1998
  36. Jan 16, 1998
Loading