>>>> "Jerry" == Jerry James
<james(a)xemacs.org> writes:
Jerry> GDB isn't.
What else is new? Attack (GCC) is always advancing in
destructiveness, and defense can't really anticipate, it just has to
hope it can cope. :-/
Jerry> How am I supposed to debug a VDB-using XEmacs?
"printf" is the obvious first suggestion.
"Don't" is my second; revert to --without-mc-alloc or even
--without-kkcc and see if the bug still occurs. This is probably a
better idea. (I wouldn't be surprised if gdb continues to segfault
uncontrollably, though. :-( )
Does XEmacs run under gdb OK if you just run it? You could try
putting a watchpoint on the members of the buffer object that
determine whether it's narrowed or not. If it's narrowed at the end,
that'll be very boring as it gets hit on every character or so. But
if it's narrowed at the beginning, you should see the problem very
quickly, as I would expect that under normal circumstances a shell
buffer grows only at the end.
--
School of Systems and Information Engineering
http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.