Please don't drop the mailing list in your replies. I've added it
back for this message.
On Mon, Dec 12, 2011 at 8:47 PM, Don Cohen
I don't know how to repeat it, but I've had a number of
problems since installing fedora 16 kde last week...
I gather that in order to get a C backtrace I need a core file
and the OS came with ulimit core size = 0. I've now changed that
so the next time I can try to use the core file.
OK, but ...
> So abrt didn't catch the crash? Or have you disabled abrt?
Is that the "automatic bug reporting tool"?
That shows some sigsegv's from usr/bin/kded4 but not xemacs.
So I guess it's not disabled.
Hmmm, it's supposed to catch crashes and store core files, even if the
user running the process has ulimit core-size = 0. I do, for example,
but I've already files 3 crash reports via abrt since installing
Fedora 16. So there's some kind of problem with abrt not noticing
that your XEmacs process crashed. How are you launching XEmacs? Via
a desktop menu? On the command line?
I guess this particular crash will go undiagnosed, and I'll be
better prepared if it happens again. Maybe. Should I be installing
xemacs-debuginfo in anticipation? Anything else?
No, let's go with what you've tried so far and see what happens.
XEmacs-Beta mailing list