From: Michael Eager <eager@eagercon.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Debugging gdb under gdb
Date: Thu, 09 Jul 2009 00:21:00 -0000 [thread overview]
Message-ID: <4A5537F3.1020100@eagercon.com> (raw)
In-Reply-To: <4A553291.8040904@vmware.com>
Michael Snyder wrote:
> Michael Eager wrote:
>> Hi --
>>
>> When I try to run a test gdb under gdb, the host gdb hangs.
>>
>> The hang occurs when the test gdb is executing pex_unix_exec_child().
>> As soon as the test gdb executes fork(), the host gdb hangs.
>> I've tried all of the permutations of follow-fork-mode
>> and detach-on-fork, with no luck. The host neither follows
>> the parent nor the child processes.
>>
>> The host gdb is "GNU gdb Fedora (6.8-32.fc10)".
>>
>> Suggestions?
>
> Are you stepping or continuing when this occurs?
>
> There is a point, somewhere around where gdb is forking the child,
> where stepping always hangs for me. I don't remember exactly where.
> I work around it by setting a breakpoint somewhere just after, and
> continuing.
I've tried both stepping and continuing. I set breakpoints in
the code shared between parent & child (where it checks the pid)
and also on both paths. None of the breakpoints are hit.
The host gdb also hangs when there are no breakpoints set and
I just run the test gdb.
> It's been a while since I've done this... but see if that helps.
The call to pex_unix_exec_child() is in find_charset_names().
My workaround is to have the host gdb force a return from
find_charset_names() in the test gdb, so it never tries to
do a fork().
--
Michael Eager eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
next prev parent reply other threads:[~2009-07-09 0:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-08 23:52 Michael Eager
2009-07-09 0:02 ` Michael Snyder
2009-07-09 0:21 ` Michael Eager [this message]
2009-07-09 15:29 ` Jan Kratochvil
2009-07-09 16:05 ` Michael Eager
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=4A5537F3.1020100@eagercon.com \
--to=eager@eagercon.com \
--cc=gdb@sourceware.org \
--cc=msnyder@vmware.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