Cog crash reports on Mac

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Cog crash reports on Mac

Igor Stasenko
 
Just a question,
could it made similar to windows or unix,
where i can see the smalltalk stack dump, recent primitives etc?

Because the crash log produced by system (i guess) don't gives much info,
just a C stack for all threads and
a list of loaded libs.

Or its technically not possible?

--
Best regards,
Igor Stasenko AKA sig.
Reply | Threaded
Open this post in threaded view
|

Re: Cog crash reports on Mac

johnmci

Unix. There was a signal handler copied over to dump the Smalltalk info on a memory fault, someone just needs to cross check the unix setup again and recopy to the osx build as likely the unix handler is more generic in what type of signals would trigger the dump now

Sent from my iPhone

On 2011-07-08, at 12:38 PM, Igor Stasenko <[hidden email]> wrote:

>
> Just a question,
> could it made similar to windows or unix,
> where i can see the smalltalk stack dump, recent primitives etc?
>
> Because the crash log produced by system (i guess) don't gives much info,
> just a C stack for all threads and
> a list of loaded libs.
>
> Or its technically not possible?
>
> --
> Best regards,
> Igor Stasenko AKA sig.
Reply | Threaded
Open this post in threaded view
|

Re: Cog crash reports on Mac

Eliot Miranda-2
In reply to this post by Igor Stasenko
 


On Fri, Jul 8, 2011 at 9:38 AM, Igor Stasenko <[hidden email]> wrote:

Just a question,
could it made similar to windows or unix,
where i can see the smalltalk stack dump, recent primitives etc?

Because the crash log produced by system (i guess) don't gives much info,
just a C stack for all threads and
a list of loaded libs.

Or its technically not possible?

So far I've not found out how to integrate with Mac's crash system.  They keep the source closed :(  However, kill -USR1 now does produce an all stacks backtrace on the Mac.  Anyone who knows more about Apple's crash handler and whether it can be augmented please let us know.
 

--
Best regards,
Igor Stasenko AKA sig.



--
best,
Eliot

Reply | Threaded
Open this post in threaded view
|

Re: Cog crash reports on Mac

johnmci

I don't thnk there is a way since those reports are send to apple if
you ask so I doubt Apple wants to clutter it up with app specific
debug info, also think of the security and
disclosure issues.

However this does not mean you can't dump stuff to the console log via
a UNIX signal handler (sudden death occurred)...
Later why you could even use a bit of FFI and ask for the bits out of
the console log. I do that for the iPhone, use one of my apps, punch
the email, I get the console log from the iOS device.

On Fri, Jul 8, 2011 at 12:49 PM, Eliot Miranda <[hidden email]> wrote:

>
>
>
> On Fri, Jul 8, 2011 at 9:38 AM, Igor Stasenko <[hidden email]> wrote:
>>
>> Just a question,
>> could it made similar to windows or unix,
>> where i can see the smalltalk stack dump, recent primitives etc?
>>
>> Because the crash log produced by system (i guess) don't gives much info,
>> just a C stack for all threads and
>> a list of loaded libs.
>>
>> Or its technically not possible?
>
> So far I've not found out how to integrate with Mac's crash system.  They keep the source closed :(  However, kill -USR1 now does produce an all stacks backtrace on the Mac.  Anyone who knows more about Apple's crash handler and whether it can be augmented please let us know.
>
>>
>> --
>> Best regards,
>> Igor Stasenko AKA sig.
>
>
>
> --
> best,
> Eliot
>
>



--
===========================================================================
John M. McIntosh <[hidden email]>
Corporate Smalltalk Consulting Ltd.  http://www.smalltalkconsulting.com
===========================================================================