Changeset 4204 for trunk/etc/DEBUG
- Timestamp:
- 05/01/07 18:04:59 (2 years ago)
- Files:
-
- trunk/etc/DEBUG (modified) (2 diffs)
Legend:
- Unmodified
- Added
- Removed
- Modified
- Copied
- Moved
trunk/etc/DEBUG
r4200 r4204 568 568 Once you discover the corrupted Lisp object or data structure, grep 569 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 try570 corruption. If looking at the sources doesn't help, you could try 571 571 setting a watchpoint on the corrupted data, and see what code modifies 572 572 it in some invalid way. (Obviously, this technique is only useful for … … 732 732 disassembly will probably show several source lines followed by a 733 733 block of assembler for those lines. The actual point where Emacs 734 crashes will be one of those source lines, but not nec cesarily the one734 crashes will be one of those source lines, but not necessarily the one 735 735 that the debugger reports. 736 736
