using -current... gdb does not seem to get along well under vmware... doing "gdb a.out" with a "break main" followed by "run" results in the behaviour seen here: ... ptrace(0x21,0xebbe,0xbfbfdc90,0x0,0x28277130) = 0 (0x0) ptrace(0x25,0xebbe,0xbfbfddd4,0x0,0x8) = 0 (0x0) ptrace(0x7,0xebbe,0x1,0x14,0x10202) = 0 (0x0) wait4(0xffffffff,0xbfbfdf08,0x0,0x0,0x28369569) = 60350 (0xebbe) kill(60350,0) = 0 (0x0) ptrace(0x21,0xebbe,0xbfbfdc90,0x0,0x28277130) = 0 (0x0) ptrace(0x25,0xebbe,0xbfbfddd4,0x0,0x8) = 0 (0x0) ptrace(0x7,0xebbe,0x1,0x14,0x10202) = 0 (0x0) wait4(0xffffffff,0xbfbfdf08,0x0,0x0,0x28369569) = 60350 (0xebbe) kill(60350,0) = 0 (0x0) ptrace(0x21,0xebbe,0xbfbfdc90,0x0,0x28277130) = 0 (0x0) ptrace(0x25,0xebbe,0xbfbfddd4,0x0,0x8) = 0 (0x0) ptrace(0x7,0xebbe,0x1,0x14,0x10202) = 0 (0x0) wait4(0xffffffff,0xbfbfdf08,0x0,0x0,0x28369569) = 60350 (0xebbe) kill(60350,0) = 0 (0x0) ptrace(0x21,0xebbe,0xbfbfdc90,0x0,0x28277130) = 0 (0x0) ptrace(0x25,0xebbe,0xbfbfddd4,0x0,0x8) = 0 (0x0) ... and gdb goes out to lunch without returning. And with a ^C, I get it all nice and hung up: 60349 p0- TX 0:27.46 gdb a.out 60350 p0- TX 0:15.39 /bin/csh -c exec /usr/home/darrenr/a.out 60369 p4 I+ 0:00.20 truss -p 60349 It requires a "kill -9" on the truss to restore life. Does anyone have any ideas about where to start trying to resolve this problem? Thanks, DarrenReceived on Wed Jul 04 2007 - 06:41:24 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:13 UTC