site_archiver@lists.apple.com Delivered-To: cocoa-dev@lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=simple/simple; d=uni-bremen.de; s=2019; t=1706643115; i=@uni-bremen.de; bh=sqI9oQfm4SA6ieIdmZuLh2X/VYLFSTkXMofpePBkPM0=; h=From:Date:References:To:In-Reply-To; b=iJ9gtAB80UL+G3qlA31ewDTQ+cYGR21oNK+whYizdvTosMoH2q1q9b0JZQTP2FZmM SpxWcurC6iqPReubvkoqFCrcuUEzp5Bh2udJAib9Bv7ZBEEwn18av9OQZHzQMfzTUH siAeu81yVxVUtSKjKobgPZ55za4MYwzerZg2VzEgadDbebyU/x+f61l3rGYon+6w0C qGwkOitd2PIzSs662/I1FfaDPLfm6qBKui55JRga/7l38lSxy3BsVLTV9sqtIP+rVD JFltB+vOH2G2PUvCW6RR/U5epU3krT7HCDm96UjGhjsyGO/Kn1qxfS5vAOKQmoq/KI Vec3UVWYo1ZUA== I am setting up a signal handler in my app like this: void *e = signal( SIGUSR1, signal_handler ); if ( e == SIG_ERR ) ... It works (i can 'kill -30 <pid>'), BUT ONLY, if I run my app outside of Xcode. When I launch it from Xcode, and I send a SIGUSR1 to my app, it always breaks at mach_msg2_trap. Obviously, this is a bit tedious for developing, since now I always have to go through Product / Archive / Distribute ... Any ideas, how I can prevent this from happening? And it's unclear to me what's going on. Can Xcode really prevent signal(3) from installing a signal handler? Or does a kill on the command line deliver the signal to several processes, one of them, maybe, an ancillary process from Xcode? Best regards, Gabriel _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/site_archiver%40lists.appl... This email sent to site_archiver@lists.apple.com smime.p7s