From: Luis Machado <luisgpm@linux.vnet.ibm.com>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: Pedro Alves <pedro@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: linux native async mode support
Date: Wed, 19 Mar 2008 16:25:00 -0000 [thread overview]
Message-ID: <1205943875.32489.10.camel@gargoyle.br.ibm.com> (raw)
In-Reply-To: <18400.36720.580645.362838@kahikatea.snap.net.nz>
Hi folks,
I've ran the testsuite on PPC to check for regressions due to the async
patch. The results look good, just the expected regressions and one
unexpected (mi2-simplerun.exp).
define.exp:
FAIL: gdb.base/define.exp: use user command: nextwhere
FAIL: gdb.base/define.exp: use hook-stop command
commands.exp:
FAIL: gdb.base/commands.exp: running to factorial in runto
FAIL: gdb.base/commands.exp: if test in test_command_prompt_position
FAIL: gdb.base/commands.exp: run factorial until breakpoint
mi2-simplerun.exp:
FAIL: gdb.mi/mi2-simplerun.exp: continue to end (1)
Nick, i still can reproduce the last one constantly.
Best regards,
On Wed, 2008-03-19 at 15:58 +1200, Nick Roberts wrote:
> I've rebuilt with your new patch.
>
> > > FAIL: gdb.mi/mi-var-child-f.exp: mi runto MAIN__ (timeout)
>
> This one has gone.
>
> > > FAIL: gdb.mi/mi-var-child-f.exp: create local variable array
>
> Looks like a buffering problem:
>
> 000-exec-run
> 000^running
> (gdb)
> 000*stopped,thread-id="0",frame={addr="0x0804859a",func="MAIN__",args=[],file="../../../gdb/testsuite/gdb.mi/array.f",fullname="/extra/src-prus/gdb/testsuite/gdb.mi/array.f",line="18"}
> (gdb)
> PASS: gdb.mi/mi-var-child-f.exp: mi runto MAIN__
> -var-create array * array
> ~"Current language: auto; currently fortran\n"
> ^done,name="array",numchild="3",value="[3]",type="integer (2,-1:1)"
> (gdb)
> FAIL: gdb.mi/mi-var-child-f.exp: create local variable array
>
> > > FAIL: gdb.mi/mi2-simplerun.exp: continue to end (1)
>
> Ditto.
>
> 999-exec-continue
> 999^running
> Hello, World!callme
> callme
> (gdb)
> 999*stopped,reason="exited-normally"
> (gdb)
> FAIL: gdb.mi/mi2-simplerun.exp: continue to end (1)
>
> > > FAIL: gdb.threads/pthreads.exp: check backtrace from main thread
>
> The backtrace was looking at the wrong thread but this has gone now.
>
> --
> Nick http://www.inet.net.nz/~nickrob
--
Luis Machado
Software Engineer
IBM Linux Technology Center
next prev parent reply other threads:[~2008-03-19 16:25 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-14 8:11 Pedro Alves
2008-03-14 21:17 ` Daniel Jacobowitz
2008-03-17 16:05 ` Pedro Alves
2008-03-17 22:05 ` Daniel Jacobowitz
2008-03-18 23:27 ` Pedro Alves
2008-03-18 23:58 ` Daniel Jacobowitz
2008-03-21 15:55 ` Daniel Jacobowitz
2008-03-21 17:19 ` Pedro Alves
2008-03-28 14:48 ` Maciej W. Rozycki
2008-03-28 16:07 ` Pedro Alves
2008-03-28 16:13 ` Daniel Jacobowitz
2008-03-28 16:40 ` Pedro Alves
2008-03-18 0:06 ` Nick Roberts
2008-03-18 23:28 ` Pedro Alves
2008-03-19 3:59 ` Nick Roberts
2008-03-19 16:25 ` Luis Machado [this message]
2008-03-19 23:19 ` Pedro Alves
2008-03-19 23:26 ` Pedro Alves
2008-03-20 1:58 ` Nick Roberts
2008-03-21 15:47 ` Daniel Jacobowitz
2008-03-21 15:49 ` Daniel Jacobowitz
2008-03-21 23:02 ` Nick Roberts
2008-03-22 1:25 ` Daniel Jacobowitz
2008-03-22 22:06 ` Nick Roberts
2008-04-01 14:00 ` Daniel Jacobowitz
2008-04-01 15:17 ` Vladimir Prus
2008-04-01 20:09 ` Nick Roberts
2008-04-04 12:34 ` Vladimir Prus
2008-04-05 17:20 ` Nick Roberts
2008-04-05 22:07 ` Vladimir Prus
2008-04-07 0:06 ` Nick Roberts
2008-04-07 2:33 ` Nick Roberts
2008-03-18 2:47 ` Nick Roberts
2008-03-14 23:10 ` Nick Roberts
2008-03-15 1:58 ` Pedro Alves
2008-03-15 3:11 ` Daniel Jacobowitz
2008-03-17 23:41 ` Nick Roberts
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=1205943875.32489.10.camel@gargoyle.br.ibm.com \
--to=luisgpm@linux.vnet.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=nickrob@snap.net.nz \
--cc=pedro@codesourcery.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