|
From: Dennis L. <pla...@gm...> - 2005-01-25 20:39:08
|
At 18:48 25.01.2005, you wrote: >When trying to debug a problem I came across this oddity, for some >reason one of my programs is claiming to die with signal 0. I ran kill >-l to check if this was a real signal as I'm sure they start at 1. > >Anyway 'kill -l 0' seems to give different output when run inside of V. >I'm running 2.2.0 (from debian unstable) but this is reproducible with >CVS sources as well. > >$ kill -l 0 >T >$ valgrind -q kill -l 0 >0 >$ valgrind --version >valgrind-2.2.0 > >Ashley, Its the same here... of course... since kill -l 0 invokes the kill builtin from the current shell, and valgrinding it invokes /bin/kill. doing /bin/kill on cmd line gives the same as in valgrind here. I think its the same there (i.e. the first is the builtin kill from ur shell) greets Dennis Carpe quod tibi datum est |