Re: Core dumps on MacOS X
Re: Core dumps on MacOS X
- Subject: Re: Core dumps on MacOS X
- From: "Bill Northcott" <email@hidden>
- Date: Sun, 15 Jun 2003 13:04:13 +1000
Thanks for the thoughts which confirmed that I was using the correct
syntax.
Actually you need to check something else as well:
In the preferences for the Console app there is an option 'Enable crash
reporting'. If this is selected you will get a crash log entry but no
core dump regardless of the limit setting.
Even this does not solve my problem.
I am trying to trace a crash in the Apple gcc compiler. This occurs if
you try to compile an Objective-C program containing a main() function
with the -fgnu-runtime flag enabled. It does not occur in compilers built
from the FSF sources.
The crash occurs in cc1obj and it was this that I wanted to crash dump.
However, cc1obj is driven by gcc and this traps the crash before it gets
to dump and just gives you an error message saying report the crash to
Apple. (I did and they classified it as uninteresting!)
There are only a couple of places in the gcc sources where
-fgnu-runtime/-fnext-runtime flags are operative. I am fairly sure the
problem is in gcc/objc-act.c but that is nearly 10,000 lines of C code
with a large number of conditionals on the runtime flags. So I need to
get a little closer.
I think I will try it on the FSF gcc mail lists.
Bill Northcott
Mark Dalrymple <email@hidden> wrote on 14/06/2003 12:18:51 AM:
>
Or if you're in the C shell:
>
% ./a.out
>
Segmentation fault
>
% limit coredumpsize unlimited
>
% ./a.out
>
Segmentation fault (core dumped)
>
The core files get deposited in /cores.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.