• 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: signal(SIGUSR2, SIG_IGN) not respected by Xcode/GDB?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: signal(SIGUSR2, SIG_IGN) not respected by Xcode/GDB?


  • Subject: Re: signal(SIGUSR2, SIG_IGN) not respected by Xcode/GDB?
  • From: Påhl Melin <email@hidden>
  • Date: Wed, 25 Mar 2009 14:05:32 +0100

2009/3/25 Ken Thomases <email@hidden>:
> Ignoring a signal doesn't prevent it from being delivered.  GDB is stopping
> at the point of delivery, _before_ any decision has been made about how to
> handle the signal.  The fact that the process will ignore the signal is
> something that is _about to happen_ in the scenario you describe.  If you
> were to issue the "signal SIGUSR2" command in the debugger, your program
> would proceed just as it would when not debugging.
>
> Furthermore, if you had issued the command "handle SIGUSR2 nostop noprint
> pass" prior to starting your program, GDB wouldn't even have stopped.

Thanks for the explanation. I wasn't aware that GDB's default
behaviour is to stop on a signal even when it programatically is
supposed to be ignored. But since it does, the behavior is expected.

Do you know any way of issuing a command (like "handle SIGUSR2 nostop
noprint pass") before starting a debug session in Xcode?

>> ...but when I type something at the prompt it just ignores it –
>> nothing happens when pressing return.
>
> This is a more fundamental problem that has nothing to do with signals.
>
> I recall seeing a problem about that go by recently on the xcode-users
> mailing list.  Check the recent archives for that list.  Also, further
> discussion of this issue should probably be carried on there, because it's
> not really relevant to this list.

I agree, since the problem is a pure GDB issue I will move to the
xcode-users list. But thanks for the help anyway.

/ Påhl
_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >signal(SIGUSR2, SIG_IGN) not respected by Xcode/GDB? (From: Påhl Melin <email@hidden>)
 >Re: signal(SIGUSR2, SIG_IGN) not respected by Xcode/GDB? (From: Ken Thomases <email@hidden>)
 >Re: signal(SIGUSR2, SIG_IGN) not respected by Xcode/GDB? (From: Påhl Melin <email@hidden>)
 >Re: signal(SIGUSR2, SIG_IGN) not respected by Xcode/GDB? (From: Ken Thomases <email@hidden>)

  • Prev by Date: Re: How to extract the basic info from an audio file?
  • Next by Date: Overriding -dealloc on any object
  • Previous by thread: Re: signal(SIGUSR2, SIG_IGN) not respected by Xcode/GDB?
  • Next by thread: Re: signal(SIGUSR2, SIG_IGN) not respected by Xcode/GDB?
  • Index(es):
    • Date
    • Thread