Mercurial > emacs
comparison etc/DEBUG @ 90813:e6fdae9180d4
Merge from emacs--devo--0
Patches applied:
* emacs--devo--0 (patch 698-710)
- Update from CVS
- Merge from gnus--rel--5.10
* gnus--rel--5.10 (patch 216)
- Update from CVS
Revision: emacs@sv.gnu.org/emacs--unicode--0--patch-196
author | Miles Bader <miles@gnu.org> |
---|---|
date | Tue, 24 Apr 2007 21:56:25 +0000 |
parents | 4ef881a120fe 563a04f93ea0 |
children | d7172f202ab8 |
comparison
equal
deleted
inserted
replaced
90812:6137cc8ddf90 | 90813:e6fdae9180d4 |
---|---|
565 the sources to find out what high-level symbols and global variables | 565 the sources to find out what high-level symbols and global variables |
566 are involved in the crash. | 566 are involved in the crash. |
567 | 567 |
568 Once you discover the corrupted Lisp object or data structure, grep | 568 Once you discover the corrupted Lisp object or data structure, grep |
569 the sources for its uses and try to figure out what could cause the | 569 the sources for its uses and try to figure out what could cause the |
570 corruption. If looking at the sources doesn;t help, you could try | 570 corruption. If looking at the sources doesn't help, you could try |
571 setting a watchpoint on the corrupted data, and see what code modifies | 571 setting a watchpoint on the corrupted data, and see what code modifies |
572 it in some invalid way. (Obviously, this technique is only useful for | 572 it in some invalid way. (Obviously, this technique is only useful for |
573 data that is modified only very rarely.) | 573 data that is modified only very rarely.) |
574 | 574 |
575 It is also useful to look at the corrupted object or data structure in | 575 It is also useful to look at the corrupted object or data structure in |
729 debugger will sometimes report wrong line numbers, e.g., when it | 729 debugger will sometimes report wrong line numbers, e.g., when it |
730 prints the backtrace for a crash. It is usually best to look at the | 730 prints the backtrace for a crash. It is usually best to look at the |
731 disassembly to determine exactly what code is being run--the | 731 disassembly to determine exactly what code is being run--the |
732 disassembly will probably show several source lines followed by a | 732 disassembly will probably show several source lines followed by a |
733 block of assembler for those lines. The actual point where Emacs | 733 block of assembler for those lines. The actual point where Emacs |
734 crashes will be one of those source lines, but not neccesarily the one | 734 crashes will be one of those source lines, but not necessarily the one |
735 that the debugger reports. | 735 that the debugger reports. |
736 | 736 |
737 Another problematic area with the MS debugger is with variables that | 737 Another problematic area with the MS debugger is with variables that |
738 are stored in registers: it will sometimes display wrong values for | 738 are stored in registers: it will sometimes display wrong values for |
739 those variables. Usually you will not be able to see any value for a | 739 those variables. Usually you will not be able to see any value for a |