Re: core dump doing practically anything to region.
-- Steve Youngs <youngs(a)xemacs.org> spake thusly:
This one is _really_ annoying.
I'm getting core dumps anytime I do something to a region.
Recipe for crash:
C-SPC
move point somewhere to create a region
C-w (M-w works just as well, even M-x boxquote-region)
CRASH!
Okay, I don't know anything about gdb (never been inspired enough to
learn), but here's what I've been able to dredge up. I apologise if
it's not useful.
I'm hoping this one isn't my fault, although I have this fear that it
is. A stack backtrace in gdb (using 'bt' or 'where') would really help
to pin it down, though.
I find that when I get 'Cannot access memory at address ...' messages
from gdb, it's because it can't deal with the optimizations that were
enabled for that particular compile. So if you're having problems with
getting a clean backtrace, you might want to try turning off
optimizations and recompiling.
Attachments:
- attachment.sig (application/pgp-signature — 232 bytes)