On Jul 09 19:43:49, s...@spacehopper.org wrote: > On 2013-07-09, Jan Stary <h...@stare.cz> wrote: > > So the last thing in the kdump is the sucessfull call > > to the (eventually) found 'xterm'. Why is that? > > This is probably because of the setgid bit.
Is this intended? Should ktrace stop tracing a child that has setgid set? Should ktrace(1) mention it? > You could try "sudo ktrace -i xterm"... It's long: http://stare.cz/~hans/.tmp/ktrace.out http://stare.cz/~hans/.tmp/kdump.txt ... 32270 ktrace CALL execve(0x7f7ffffce570,0x7f7ffffceaf0,0x7f7ffffceb00) 32270 ktrace NAMI "/usr/X11R6/bin/xterm" 32270 xterm NAMI "/usr/libexec/ld.so" 32270 xterm EMUL "native" ... 16697 xterm CALL execve(0x58483481160,0x5847d746d00,0x58474f4b400) 16697 xterm NAMI "/usr/X11R6/bin/luit" 16697 luit NAMI "/usr/libexec/ld.so" 16697 luit EMUL "native" ... 16697 luit CALL exit(0) So luit seems to just exit normally, for some reason. Sometimes.
