* linux-nat.c:471: internal-error: unknown ptrace event 5
@ 2005-05-30 15:14 Andreas Schwab
2005-05-30 17:05 ` Daniel Jacobowitz
0 siblings, 1 reply; 4+ messages in thread
From: Andreas Schwab @ 2005-05-30 15:14 UTC (permalink / raw)
To: gdb; +Cc: Indraneel Sarkar
Why is linux_handle_extended_wait not prepared to handle
PTRACE_EVENT_VFORK_DONE?
LLW: waitpid 8077 received Trace/breakpoint trap (stopped)
LLW: Handling extended status 0x02057f
LLTA: PTRACE_PEEKUSER LWP 8077, 0, 0 (OK)
LLW: Candidate event Trace/breakpoint trap (stopped) in LWP 8077.
SC: kill LWP 8522 **<SIGSTOP>**
SC: lwp kill 0 ERRNO-OK
SC: kill LWP 8513 **<SIGSTOP>**
SC: lwp kill 0 ERRNO-OK
SC: kill LWP 8511 **<SIGSTOP>**
SC: lwp kill 0 ERRNO-OK
SC: kill LWP 8503 **<SIGSTOP>**
SC: lwp kill 0 ERRNO-OK
SC: kill LWP 8502 **<SIGSTOP>**
SC: lwp kill 0 ERRNO-OK
SC: kill LWP 8501 **<SIGSTOP>**
SC: lwp kill 0 ERRNO-OK
SC: kill LWP 8072 **<SIGSTOP>**
SC: lwp kill 0 ERRNO-OK
SC: kill LWP 8073 **<SIGSTOP>**
SC: lwp kill 0 ERRNO-OK
SC: kill LWP 8074 **<SIGSTOP>**
SC: lwp kill 0 ERRNO-OK
SC: kill LWP 8075 **<SIGSTOP>**
SC: lwp kill 0 ERRNO-OK
SC: kill LWP 8076 **<SIGSTOP>**
SC: lwp kill 0 ERRNO-OK
SC: kill LWP 8078 **<SIGSTOP>**
SC: lwp kill 0 ERRNO-OK
SC: kill LWP 8079 **<SIGSTOP>**
SC: lwp kill 0 ERRNO-OK
SC: kill LWP 8080 **<SIGSTOP>**
SC: lwp kill 0 ERRNO-OK
SC: kill LWP 8081 **<SIGSTOP>**
SC: lwp kill 0 ERRNO-OK
SC: kill LWP 8082 **<SIGSTOP>**
SC: lwp kill 0 ERRNO-OK
SC: kill LWP 8083 **<SIGSTOP>**
SC: lwp kill 0 ERRNO-OK
SC: kill LWP 8084 **<SIGSTOP>**
SC: lwp kill 0 ERRNO-OK
SC: kill LWP 8085 **<SIGSTOP>**
SC: lwp kill 0 ERRNO-OK
SC: kill LWP 8086 **<SIGSTOP>**
SC: lwp kill 0 ERRNO-OK
SC: kill LWP 8087 **<SIGSTOP>**
SC: lwp kill 0 ERRNO-OK
SC: kill LWP 8088 **<SIGSTOP>**
SC: lwp kill 0 ERRNO-OK
SC: kill LWP 8089 **<SIGSTOP>**
SC: lwp kill 0 ERRNO-OK
SC: kill LWP 8090 **<SIGSTOP>**
SC: lwp kill 0 ERRNO-OK
SC: kill LWP 8091 **<SIGSTOP>**
SC: lwp kill 0 ERRNO-OK
SC: kill LWP 8092 **<SIGSTOP>**
SC: lwp kill 0 ERRNO-OK
SC: kill LWP 8093 **<SIGSTOP>**
SC: lwp kill 0 ERRNO-OK
SC: kill LWP 8094 **<SIGSTOP>**
SC: lwp kill 0 ERRNO-OK
SC: kill LWP 8095 **<SIGSTOP>**
SC: lwp kill 0 ERRNO-OK
SC: kill LWP 8096 **<SIGSTOP>**
SC: lwp kill 0 ERRNO-OK
SC: kill LWP 8097 **<SIGSTOP>**
SC: lwp kill 0 ERRNO-OK
SC: kill LWP 8288 **<SIGSTOP>**
SC: lwp kill 0 ERRNO-OK
SC: kill LWP 8289 **<SIGSTOP>**
SC: lwp kill 0 ERRNO-OK
SC: kill LWP 8290 **<SIGSTOP>**
SC: lwp kill 0 ERRNO-OK
SC: kill LWP 8291 **<SIGSTOP>**
SC: lwp kill 0 ERRNO-OK
SC: kill LWP 8292 **<SIGSTOP>**
SC: lwp kill 0 ERRNO-OK
SC: kill LWP 8293 **<SIGSTOP>**
SC: lwp kill 0 ERRNO-OK
SC: kill LWP 8294 **<SIGSTOP>**
SC: lwp kill 0 ERRNO-OK
SC: kill LWP 8295 **<SIGSTOP>**
SC: lwp kill 0 ERRNO-OK
SC: kill LWP 8296 **<SIGSTOP>**
SC: lwp kill 0 ERRNO-OK
SC: kill LWP 8303 **<SIGSTOP>**
SC: lwp kill 0 ERRNO-OK
SC: kill LWP 8309 **<SIGSTOP>**
SC: lwp kill 0 ERRNO-OK
SC: kill LWP 8322 **<SIGSTOP>**
SC: lwp kill 0 ERRNO-OK
SC: kill LWP 8071 **<SIGSTOP>**
SC: lwp kill 0 ERRNO-OK
WL: waitpid LWP 8522 received Stopped (signal) (stopped)
WL: waitpid LWP 8513 received Stopped (signal) (stopped)
WL: waitpid LWP 8511 received Stopped (signal) (stopped)
WL: waitpid LWP 8503 received Stopped (signal) (stopped)
WL: waitpid LWP 8502 received Stopped (signal) (stopped)
WL: waitpid LWP 8501 received Stopped (signal) (stopped)
WL: waitpid LWP 8072 received Stopped (signal) (stopped)
WL: waitpid LWP 8073 received Stopped (signal) (stopped)
WL: waitpid LWP 8074 received Stopped (signal) (stopped)
WL: waitpid LWP 8075 received Stopped (signal) (stopped)
WL: waitpid LWP 8076 received Stopped (signal) (stopped)
WL: waitpid LWP 8078 received Stopped (signal) (stopped)
WL: waitpid LWP 8079 received Stopped (signal) (stopped)
WL: waitpid LWP 8080 received Stopped (signal) (stopped)
WL: waitpid LWP 8081 received Stopped (signal) (stopped)
WL: waitpid LWP 8082 received Stopped (signal) (stopped)
WL: waitpid LWP 8083 received Stopped (signal) (stopped)
WL: waitpid LWP 8084 received Stopped (signal) (stopped)
WL: waitpid LWP 8085 received Stopped (signal) (stopped)
WL: waitpid LWP 8086 received Stopped (signal) (stopped)
WL: waitpid LWP 8087 received Stopped (signal) (stopped)
WL: waitpid LWP 8088 received Stopped (signal) (stopped)
WL: waitpid LWP 8089 received Stopped (signal) (stopped)
WL: waitpid LWP 8090 received Stopped (signal) (stopped)
WL: waitpid LWP 8091 received Stopped (signal) (stopped)
WL: waitpid LWP 8092 received Stopped (signal) (stopped)
WL: waitpid LWP 8093 received Stopped (signal) (stopped)
WL: waitpid LWP 8094 received Stopped (signal) (stopped)
WL: waitpid LWP 8095 received Stopped (signal) (stopped)
WL: waitpid LWP 8096 received Stopped (signal) (stopped)
WL: waitpid LWP 8097 received Stopped (signal) (stopped)
WL: waitpid LWP 8288 received Stopped (signal) (stopped)
WL: waitpid LWP 8289 received Stopped (signal) (stopped)
WL: waitpid LWP 8290 received Stopped (signal) (stopped)
WL: waitpid LWP 8291 received Stopped (signal) (stopped)
WL: waitpid LWP 8292 received Stopped (signal) (stopped)
WL: waitpid LWP 8293 received Stopped (signal) (stopped)
WL: waitpid LWP 8294 received Stopped (signal) (stopped)
WL: waitpid LWP 8295 received Stopped (signal) (stopped)
WL: waitpid LWP 8296 received Stopped (signal) (stopped)
WL: waitpid LWP 8303 received Stopped (signal) (stopped)
WL: waitpid LWP 8309 received Stopped (signal) (stopped)
WL: waitpid LWP 8322 received Stopped (signal) (stopped)
WL: waitpid LWP 8071 received Stopped (signal) (stopped)
LLW: trap_ptid is LWP 8077.
Attaching after fork to child process 8547.
RC: PTRACE_CONT LWP 8522, 0, 0 (resume sibling)
RC: PTRACE_CONT LWP 8513, 0, 0 (resume sibling)
RC: PTRACE_CONT LWP 8511, 0, 0 (resume sibling)
RC: PTRACE_CONT LWP 8503, 0, 0 (resume sibling)
RC: PTRACE_CONT LWP 8502, 0, 0 (resume sibling)
RC: PTRACE_CONT LWP 8501, 0, 0 (resume sibling)
RC: PTRACE_CONT LWP 8072, 0, 0 (resume sibling)
RC: PTRACE_CONT LWP 8073, 0, 0 (resume sibling)
RC: PTRACE_CONT LWP 8074, 0, 0 (resume sibling)
RC: PTRACE_CONT LWP 8075, 0, 0 (resume sibling)
RC: PTRACE_CONT LWP 8076, 0, 0 (resume sibling)
RC: PTRACE_CONT LWP 8077, 0, 0 (resume sibling)
RC: PTRACE_CONT LWP 8078, 0, 0 (resume sibling)
RC: PTRACE_CONT LWP 8079, 0, 0 (resume sibling)
RC: PTRACE_CONT LWP 8080, 0, 0 (resume sibling)
RC: PTRACE_CONT LWP 8081, 0, 0 (resume sibling)
RC: PTRACE_CONT LWP 8082, 0, 0 (resume sibling)
RC: PTRACE_CONT LWP 8083, 0, 0 (resume sibling)
RC: PTRACE_CONT LWP 8084, 0, 0 (resume sibling)
RC: PTRACE_CONT LWP 8085, 0, 0 (resume sibling)
RC: PTRACE_CONT LWP 8086, 0, 0 (resume sibling)
RC: PTRACE_CONT LWP 8087, 0, 0 (resume sibling)
RC: PTRACE_CONT LWP 8088, 0, 0 (resume sibling)
RC: PTRACE_CONT LWP 8089, 0, 0 (resume sibling)
RC: PTRACE_CONT LWP 8090, 0, 0 (resume sibling)
RC: PTRACE_CONT LWP 8091, 0, 0 (resume sibling)
RC: PTRACE_CONT LWP 8092, 0, 0 (resume sibling)
RC: PTRACE_CONT LWP 8093, 0, 0 (resume sibling)
RC: PTRACE_CONT LWP 8094, 0, 0 (resume sibling)
RC: PTRACE_CONT LWP 8095, 0, 0 (resume sibling)
RC: PTRACE_CONT LWP 8096, 0, 0 (resume sibling)
RC: PTRACE_CONT LWP 8097, 0, 0 (resume sibling)
RC: PTRACE_CONT LWP 8288, 0, 0 (resume sibling)
RC: PTRACE_CONT LWP 8289, 0, 0 (resume sibling)
RC: PTRACE_CONT LWP 8290, 0, 0 (resume sibling)
RC: PTRACE_CONT LWP 8291, 0, 0 (resume sibling)
RC: PTRACE_CONT LWP 8292, 0, 0 (resume sibling)
RC: PTRACE_CONT LWP 8293, 0, 0 (resume sibling)
RC: PTRACE_CONT LWP 8294, 0, 0 (resume sibling)
RC: PTRACE_CONT LWP 8295, 0, 0 (resume sibling)
RC: PTRACE_CONT LWP 8296, 0, 0 (resume sibling)
RC: PTRACE_CONT LWP 8303, 0, 0 (resume sibling)
RC: PTRACE_CONT LWP 8309, 0, 0 (resume sibling)
RC: PTRACE_CONT LWP 8322, 0, 0 (resume sibling)
RC: PTRACE_CONT LWP 8071, 0, 0 (resume sibling)
LLR: PTRACE_CONT process 8547, 0 (resume event thread)
LLW: waitpid 8077 received Trace/breakpoint trap (stopped)
LLW: Handling extended status 0x05057f
linux-nat.c:471: internal-error: unknown ptrace event 5
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: linux-nat.c:471: internal-error: unknown ptrace event 5
2005-05-30 15:14 linux-nat.c:471: internal-error: unknown ptrace event 5 Andreas Schwab
@ 2005-05-30 17:05 ` Daniel Jacobowitz
2005-05-31 14:10 ` Andreas Schwab
0 siblings, 1 reply; 4+ messages in thread
From: Daniel Jacobowitz @ 2005-05-30 17:05 UTC (permalink / raw)
To: Andreas Schwab; +Cc: gdb, Indraneel Sarkar
On Mon, May 30, 2005 at 05:14:25PM +0200, Andreas Schwab wrote:
> Why is linux_handle_extended_wait not prepared to handle
> PTRACE_EVENT_VFORK_DONE?
Because it should absolutely never, ever receive it.
PTRACE_EVENT_VFORK should be reported, then the next time we resume
child_follow_fork should be called, and that should consume the
PTRACE_EVENT_VFORK_DONE.
You didn't say what version of GDB you're using. There've been some
changes lately.
> LLW: waitpid 8077 received Trace/breakpoint trap (stopped)
> LLW: Handling extended status 0x02057f
> LLTA: PTRACE_PEEKUSER LWP 8077, 0, 0 (OK)
> LLW: Candidate event Trace/breakpoint trap (stopped) in LWP 8077.
> SC: kill LWP 8522 **<SIGSTOP>**
> SC: lwp kill 0 ERRNO-OK
...
> WL: waitpid LWP 8071 received Stopped (signal) (stopped)
> LLW: trap_ptid is LWP 8077.
> Attaching after fork to child process 8547.
> RC: PTRACE_CONT LWP 8522, 0, 0 (resume sibling)
...
> LLR: PTRACE_CONT process 8547, 0 (resume event thread)
> LLW: waitpid 8077 received Trace/breakpoint trap (stopped)
> LLW: Handling extended status 0x05057f
> linux-nat.c:471: internal-error: unknown ptrace event 5
It looks like you're using 'set follow child'. Is that right? If so,
it looks like I never extensively tested the child-side path using
multiple threads; that would make sense, since when I wrote it NPTL was
very new, and LinuxThreads doesn't use vfork with threads. It will
need a bit of work; the problem is that we are bypassing target_detach
for the vfork, but we really do want to detach. Just not yet.
--
Daniel Jacobowitz
CodeSourcery, LLC
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: linux-nat.c:471: internal-error: unknown ptrace event 5
2005-05-30 17:05 ` Daniel Jacobowitz
@ 2005-05-31 14:10 ` Andreas Schwab
0 siblings, 0 replies; 4+ messages in thread
From: Andreas Schwab @ 2005-05-31 14:10 UTC (permalink / raw)
To: gdb; +Cc: Indraneel Sarkar
Daniel Jacobowitz <drow@false.org> writes:
> You didn't say what version of GDB you're using. There've been some
> changes lately.
This was tested with gdb 9.3.
> It looks like you're using 'set follow child'. Is that right?
I don't know. Indraneel, do you?
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: linux-nat.c:471: internal-error: unknown ptrace event 5
@ 2005-05-31 14:27 Indraneel Sarkar
0 siblings, 0 replies; 4+ messages in thread
From: Indraneel Sarkar @ 2005-05-31 14:27 UTC (permalink / raw)
To: gdb, schwab
Yes, it was with gdb 9.3. And yes, follow-fork-mode is set to child.
Thanks,
-Indraneel
>>> Andreas Schwab <schwab@suse.de> 05/31/05 8:09 am >>>
Daniel Jacobowitz <drow@false.org> writes:
> You didn't say what version of GDB you're using. There've been some
> changes lately.
This was tested with gdb 9.3.
> It looks like you're using 'set follow child'. Is that right?
I don't know. Indraneel, do you?
Andreas.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2005-05-31 14:27 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-05-30 15:14 linux-nat.c:471: internal-error: unknown ptrace event 5 Andreas Schwab
2005-05-30 17:05 ` Daniel Jacobowitz
2005-05-31 14:10 ` Andreas Schwab
2005-05-31 14:27 Indraneel Sarkar
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox