Stephen J. Turnbull wrote:
> Ed> I'm having trouble persuading xemacs to make a core dump on my
> Ed> Linux system, despite 'ulimit -c unlimited' and getting core
> Ed> dumps from ordinary C programs that crash.
>How do you start xemacs?
>From a shell script looking roughly like
exec xemacs -geometry 120x78+0+0
> Ed> To diagnose this, is there a way I can force xemacs to crash?
>Untested, but kill -SEGV $xemacs_pid should do it.
Yes, and that does leave a coredump. It's strange that I don't get one
for the assertion failure. I'll investigate some more.
> Ed> M-x crash-and-dump-core?
>That's an interesting concept for a debug build, but we certainly
>wouldn't implement that function in a production build. ;-)
I think a better function for me would be M-x assertion-failure, to
specifically test what happens when assert() in the C code returns
Ed Avis <avised(a)kbcfp.com>
This message may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived by any transmission to an unintended recipient. If you are not an intended recipient, please notify the sender and delete this message immediately. Any views expressed in this message are those of the sender, not those of KBC Financial Products or any affiliate thereof.
This message does not create any obligation, contractual or otherwise, on the part of any such entity. It is not an offer (or solicitation of an offer) of, or a recommendation to buy or sell, any financial product. Any prices or other values included in this message are indicative only, and do not necessarily represent current market prices, the prices at which any KBC entity would enter into a transaction or the prices at which similar transactions may be carried on that entity's own books. The information contained in this message is provided "as is", without representations or warranties, express or implied, of any kind. Past performance is not indicative of future returns.