Re: ECX_BAD_ACCESS again
Re: ECX_BAD_ACCESS again
- Subject: Re: ECX_BAD_ACCESS again
- From: Robert Bielik <email@hidden>
- Date: Sat, 05 Jan 2008 14:07:15 +0100
Thanks Jonas,
Jonas Maebe wrote:
One warning about this: for i386 (Intel 32 bit), passing arguments is
not going to work like that in C because the default calling
convention there passes everything on the stack (while ours is
fastcall, where the first three parameters are passed in registers).
You may be able to declare your handler in gcc also as fastcall to
work around this, but I don't know by heart how this is done. Or you
may simply not pass any parameters at all.
Ok, nice! As I know exactly where and when the exception might be
thrown, I don't need to pass any params. As an aside, is there a way to
register signal handlers scope-wise? That is, only to intercept a signal
within a specific scope? Even though the library call is the only place
where this happens, I guess that signal handling is global for the
entire process?
/R
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden