Hello, Thanks for the insight, that did the trick nicely.
I agree with Ben that it's pointless to ignore uncatchable signals. However, for backward's compatibility sake, it would be nice to actually keep the old behavior and emit a a warning. In my case, I was using 0.8 when I installed the shorty library and I could get started with the library because the example supplied just worked. Now, had I seen the barbaric trace, I would probably have given up immediately and looked somewhere else, wouldn't that have been a shame? :-) Cheers JM Le mercredi 12 juin 2013 18:13:02 UTC+4, Ben Noordhuis a écrit : > > On Wed, Jun 12, 2013 at 4:01 PM, Bert Belder > <[email protected]<javascript:>> > wrote: > > > > On Wednesday, June 12, 2013 3:25:46 PM UTC+2, Jean-Michel Hiver wrote: > >> > >> Hello List, > >> > >> I am using a modified version of the "shorty" library > >> https://github.com/mtd/shorty > >> > >> Looks like it has issues with 0.10 though: > >> > >> node client.js > >> > >> node.js:762 > >> throw errnoException(process._errno, 'uv_signal_start'); > >> ^ > >> Error: uv_signal_start EINVAL > >> at errnoException (node.js:540:13) > >> at process.on.process.addListener (node.js:762:17) > >> at Object.<anonymous> (/mnt/Bushido/client.js:145:9) > >> at Module._compile (module.js:456:26) > >> at Object.Module._extensions..js (module.js:474:10) > >> at Module.load (module.js:356:32) > >> at Function.Module._load (module.js:312:12) > >> at Function.Module.runMain (module.js:497:10) > >> at startup (node.js:119:16) > >> at node.js:901:3 > >> > >> On 0.8 it works fine. > >> > >> How do I go about debugging this issue? I'm fairly new to node.js (I > come > >> from a Perl background but Net::SMPP didn't work for me so I used this > >> library instead) so I don't quite know how to debug this. > >> > >> Thanks in advance for your insights. > >> > >> Cheers > >> JM > > > > > > Nevermind my previous reply. > > > > This suggests that you are installing handlers for SIGKILL and SIGSTOP, > > which I suggest you don't. SIGKILL and SIGSTOP are uncatchable anyway so > > those handlers have no effect at best. (besides, SIGSTOP has no business > in > > that list anyway because it has nothing to do with the process > terminating.) > > > > This issue comes from the fact that since v0.10 libuv no longer silently > > ignores sigaction() failure when starting a signal watcher, which > happens > > when a signal doesn't exist or is uncatchable. Invalid signals are > "filtered > > out" by node but uncatchable ones aren't. > > > > Ben / Isaac, is this something we should fix? We could make node ignore > > SIGKILL and SIGSTOP or restore the 0.10 behavior for uv_signal. > > Well, it's like you say - they're uncatchable. Silently ignoring them > would just give people a false sense of security. > -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
