• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: catching EXC_BAD_ACCESS?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: catching EXC_BAD_ACCESS?


  • Subject: Re: catching EXC_BAD_ACCESS?
  • From: Brad Parker <email@hidden>
  • Date: Mon, 21 Nov 2005 12:06:07 -0500
  • Organization: Heeltoe Consulting

Jonas Maebe wrote:
>
>On 21 nov 2005, at 15:43, Jonas Maebe wrote:
>
>> I've now tried a 64bit version and sure enough, that one always
>> crashes with a SIGBUS when returning from the signal handler, even
>> if the handler doesn't do anything. Warrants a radar, I'd say. I've
>> put the adjusted 64bit version of the test program below (which, as
>> I said, crashes even if you remove all code from "signal_handler"):
>
>Found the solution! Change
>
>>   sa.sa_flags = SA_SIGINFO;
>
>into
>
>sa.sa_flags = SA_SIGINFO|SA_64REGSET;

heh.  I added that to my FPE test program and the machine hung hard.  I had
to power cycle :-)

it's a imac G5.

-brad
 _______________________________________________
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

  • Follow-Ups:
    • Re: catching EXC_BAD_ACCESS?
      • From: "Jordan K. Hubbard" <email@hidden>
References: 
 >Re: catching EXC_BAD_ACCESS? (From: Jonas Maebe <email@hidden>)

  • Prev by Date: Re: How to find out if running on new dual core G5
  • Next by Date: Re: catching EXC_BAD_ACCESS?
  • Previous by thread: Re: catching EXC_BAD_ACCESS?
  • Next by thread: Re: catching EXC_BAD_ACCESS?
  • Index(es):
    • Date
    • Thread