From: Daniel Jacobowitz <drow@false.org>
To: Denis PILAT <denis.pilat@st.com>
Cc: teawater <teawater@gmail.com>, gdb-patches <gdb-patches@sourceware.org>
Subject: Re: random results with the gdb testsuite
Date: Fri, 10 Oct 2008 12:36:00 -0000 [thread overview]
Message-ID: <20081010123530.GA7167@caradoc.them.org> (raw)
In-Reply-To: <48EF10DA.9000701@st.com>
On Fri, Oct 10, 2008 at 10:22:50AM +0200, Denis PILAT wrote:
> Here is part of the log file. At a specific time (p/f *(long long *)) it
> seems like the debugger hangs up, then all further test are UNRESOLVED.
>
> If I run this test and don't touch my keyboard, don't switch the current
> window, then it's 100% successful.
>
> If I'm using the console window intensively after having run this test,
> switching window, using keyboard, then I get the following log where
> apparently my debugger crash, or just close.
> I can't find a way to debug that problem.
Normally Windows (you did say this was Windows, right?) can be
configured to pop up a dialog when a program crashes. You can't
necessarily get into GDB from there, but you may be able to get some
kind of dump. I think the Cygwin folks have instructions on getting
stack dumps or even core dumps from that point.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-10-10 12:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-09 9:20 Denis PILAT
2008-10-09 11:25 ` teawater
2008-10-09 17:38 ` Michael Snyder
2008-10-10 8:23 ` Denis PILAT
2008-10-10 11:38 ` Mark Kettenis
2008-10-10 12:56 ` Denis PILAT
2008-10-10 12:36 ` Daniel Jacobowitz [this message]
2008-10-10 12:54 ` Denis PILAT
2008-10-10 13:03 ` Daniel Jacobowitz
2008-10-10 13:06 ` Denis PILAT
2008-10-10 17:40 ` Michael Snyder
2008-10-13 8:20 ` Denis PILAT
2008-10-13 19:26 ` Michael Snyder
2008-10-09 18:37 ` Thiago Jung Bauermann
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=20081010123530.GA7167@caradoc.them.org \
--to=drow@false.org \
--cc=denis.pilat@st.com \
--cc=gdb-patches@sourceware.org \
--cc=teawater@gmail.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