From: Jesse Marlin <jlm@compgen.com>
To: gdb@sources.redhat.com
Subject: Can't attach to child using gdb-5.1.1 on Linux
Date: Fri, 22 Mar 2002 07:32:00 -0000 [thread overview]
Message-ID: <15515.20096.343244.71499@bass.compgen.com> (raw)
I have a process that forks a child. If I try to attach to the
child it reads the symbols and shows an accurate stack trace, but when
I set a breakpoint and try to continue I get the following:
(gdb) c
Continuing.
lin-lwp.c:1003: gdb-internal-error: lin_lwp_wait: Assertion `WIFSTOPPED (status) && WSTOPSIG (status) == SIGSTOP' failed.
An internal GDB error was detected. This may make further
debugging unreliable. Continue this debugging session? (y or n) n
Create a core file containing the current state of GDB? (y or n) n
Inferior GDB exited abnormally with code 1
I answered yes to the above also, but it did not improve the situation. Has
anybody seen this behvior before. I am using gcc-2.95.3 for compilation.
next reply other threads:[~2002-03-22 15:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-22 7:32 Jesse Marlin [this message]
2002-04-04 6:26 ` Andrew Cagney
2002-04-04 6:54 ` Jesse Marlin
2002-04-04 7:44 ` Andrew Cagney
2002-04-04 8:18 ` Jesse Marlin
2002-04-07 9:06 ` Andrew Cagney
2002-04-11 14:43 ` Jesse Marlin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=15515.20096.343244.71499@bass.compgen.com \
--to=jlm@compgen.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox