Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Denis PILAT <denis.pilat@st.com>
To: teawater <teawater@gmail.com>, 	gdb-patches <gdb-patches@sourceware.org>
Subject: Re: random results with the gdb testsuite
Date: Fri, 10 Oct 2008 08:23:00 -0000	[thread overview]
Message-ID: <48EF10DA.9000701@st.com> (raw)
In-Reply-To: <daef60380810090424u2ce9fa90ge37eff7626e3dd5c@mail.gmail.com>

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.
Of course all test passed well if executed by hand !

I'm using gdb 6.8 testsuite, hosted on linux with an internal ST 
debugger based as well on gdb6.8.


$63 = 100100011010001010110011110001001101010111100110111101111
(gdb) PASS: gdb.base/long_long.exp: p/t *(long long *)ll
p/a *(long long *)ll
$64 = 0x89abcdef
(gdb) PASS: gdb.base/long_long.exp: p/a *(long long *)ll
p/f *(long long *)ll
$65 = 3.5127005640885037e-303
(gdb) PASS: gdb.base/long_long.exp: p/f *(long long *)ll
p/c *(long long *)ll
$66 = -17 'ERROR: Process no longer exists
UNRESOLVED: gdb.base/long_long.exp: p/c *(long long *)ll
ERROR: Couldn't send x/w w to GDB.
UNRESOLVED: gdb.base/long_long.exp: set examine size to w
ERROR: Couldn't send x/x w to GDB.
 ...


-- 
Denis

teawater wrote:
> I test them in GDB-cvs version a lot of times but not got any fail.
> Which testsuite and wich GDB did use?
> And maybe you can post your "gdb.log" if you don't mind.
>
> BTW Maybe you need post this mail to gdb@sourceware.org.
>
> On Thu, Oct 9, 2008 at 17:19, Denis PILAT <denis.pilat@st.com> wrote:
>   
>> Hi all
>>
>> I am having random results using the gdb testsuite (with dejagnu 1.4.4),
>> especially for some test like gdb.base/display.exp ,
>> gdb.base/long_long.exp and gdb.cp/ctti.exp.
>> Sometime they are successful, sometime 50% fails.
>>
>> Has anybody already experimented such random behavior ?
>> Thanks for your answer.
>> Denis
>>
>>
>>     
>
>   


  parent reply	other threads:[~2008-10-10  8:23 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 [this message]
2008-10-10 11:38     ` Mark Kettenis
2008-10-10 12:56       ` Denis PILAT
2008-10-10 12:36     ` Daniel Jacobowitz
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=48EF10DA.9000701@st.com \
    --to=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