• 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
gdb and mach exceptions
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

gdb and mach exceptions


  • Subject: gdb and mach exceptions
  • From: Brendan Creane <email@hidden>
  • Date: Tue, 23 May 2006 13:33:38 -0700 (PDT)

Hello All, I have a simple but still unsolved problem
involving the interaction of the EXC_BAD_ACCESS
exception and gdb: I can't figure out how to get gdb
to pass the exception to my signal handler.

My test program works fine if I send a SIGUSR1 -- gdb
passes the signal to my program and I get a breakpoint
in the signal handler.  The test program works as
expected w/o gdb -- the EXC_BAD_ACCESS invokes my
sigaction handler. But provoking a EXC_BAD_ACCESS
within gdb stalls on the offending code.

I'm curious if there is analagous gdb command "handle
SIGUSR1 nostop" for EXC_BAD_ACCESS? Is there a
different way from sigaction() to specify how to
handle the EXC_BAD_ACCESS exception?

thanks in advance for your help,
cheers, Brendan Creane
 _______________________________________________
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: gdb and mach exceptions
      • From: Jonas Maebe <email@hidden>
  • Prev by Date: Re: StartupItems
  • Next by Date: Re: StartupItems
  • Previous by thread: Dependancies, theory and practice (Was: StartupItems)
  • Next by thread: Re: gdb and mach exceptions
  • Index(es):
    • Date
    • Thread