This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: -exec-step over a blocking function call
- From: Nick Roberts <nickrob at snap dot net dot nz>
- To: Aleksandar Ristovski <ARistovski at qnx dot com>
- Cc: gdb at sourceware dot org
- Date: Thu, 20 Mar 2008 08:50:48 +1200
- Subject: Re: -exec-step over a blocking function call
- References: <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