From: Nick Roberts <nickrob@snap.net.nz>
To: Aleksandar Ristovski <ARistovski@qnx.com>
Cc: gdb@sourceware.org
Subject: Re: -exec-step over a blocking function call
Date: Wed, 19 Mar 2008 21:03:00 -0000 [thread overview]
Message-ID: <18401.31912.560280.609399@kahikatea.snap.net.nz> (raw)
In-Reply-To: <47E13AAD.9050504@qnx.com>
> Where SyncSemWait is a blocking function (as the name suggests, waiting for
> semaphore). Gdb will just sit here since the inferior has several threads,
> one
> of which is reading stdin waiting for user input, and apparently input would
>
> unblock. But until it does, gdb is sitting here. The problem I am seeing is
> that
> often, while waiting for SyncSemWait to return IDE would issue additional mi
>
> commands which eventually make gdb crash or appear frozen (unresponsive).
>
> I am not sure how should gdb deal with this situation. Any ideas?
There is a problem with gdb if it crashes. Although it might not fix your
problem, you could attach the gdb in your IDE to another instance of gdb
to catch and analyse the crash if/when it happens.
--
Nick http://www.inet.net.nz/~nickrob
prev parent reply other threads:[~2008-03-19 20:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-19 16:51 Aleksandar Ristovski
2008-03-19 19:38 ` Vladimir Prus
2008-03-19 21:03 ` Nick Roberts [this message]
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=18401.31912.560280.609399@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=ARistovski@qnx.com \
--cc=gdb@sourceware.org \
/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