Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Fix solib-disc.exp regression with x86 gdbserver
Date: Sun, 11 Apr 2010 16:13:00 -0000	[thread overview]
Message-ID: <201004111713.04169.pedro@codesourcery.com> (raw)
In-Reply-To: <h2o6dc9ffc81004110904rf71caee7oed31674949c91337@mail.gmail.com>

On Sunday 11 April 2010 17:04:28, H.J. Lu wrote:
> I got following extra failures with native gdbserver on Linux/x86-64.

Compared to what?

> Are they expected?
> 
> FAIL: gdb.ada/tasks.exp: continue to breakpoint (the program exited)
> FAIL: gdb.ada/tasks.exp: continue until end of program (the program is
> no longer running)
> FAIL: gdb.ada/tasks.exp: info tasks after hitting breakpoint
> FAIL: gdb.ada/tasks.exp: info tasks before inserting breakpoint

No clue.

> FAIL: gdb.base/break-entry.exp: running to *0x4002e0 in runto

I see this too (Linux/x86-64).

> FAIL: gdb.base/randomize.exp: fixed addresses should match

Expected, gdbserver doesn't support disabling randomization.

> FAIL: gdb.base/recurse.exp: second instance watchpoint deleted when
> leaving scope

I don't see this one.

> FAIL: gdb.base/watch-vfork.exp: Watchpoint triggers after vfork (sw)
> (the program exited)

Expected.

> FAIL: gdb.cp/exception.exp: continue to second throw

I see this too.

> FAIL: gdb.mi/mi-var-cmd.exp: in-and-out-of-scope: in scope now

I see this too.

> FAIL: gdb.threads/attach-stopped.exp: threaded: attach2, exit leaves
> process sleeping

I don't see this one.  May be a red herring -- gdbserver doesn't
support what's being tested, IIRC.

> FAIL: gdb.threads/execl.exp: continue across exec
> FAIL: gdb.threads/fork-child-threads.exp: get to the spawned thread
> (the program exited)
> FAIL: gdb.threads/fork-child-threads.exp: next over fork
> FAIL: gdb.threads/fork-child-threads.exp: two threads found

Expected, gdbserver doesn't support following exec or fork events.

> FAIL: gdb.trace/backtrace.exp: 1.13: trace in recursion: depth not equal to 3
<skip a bunch of gdb.trace failures>
> FAIL: gdb.trace/while-dyn.exp: 5.12: define ws <stepcount>

Only recently (a couple of days) have the gdb.trace/ tests started
running against gdbserver (it didn't support tracepoints before),
but, none of these fails are expected on x86_64.  The all pass
for me.  I'd like to understand them.  What are the failures like?

-- 
Pedro Alves


  reply	other threads:[~2010-04-11 16:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-11  1:52 Pedro Alves
2010-04-11 14:04 ` H.J. Lu
2010-04-11 14:18   ` Pedro Alves
2010-04-11 15:43     ` H.J. Lu
2010-04-11 16:17       ` Pedro Alves
2010-04-11 16:22         ` H.J. Lu
2010-04-11 16:59     ` H.J. Lu
2010-04-11 16:04 ` H.J. Lu
2010-04-11 16:13   ` Pedro Alves [this message]
2010-04-11 16:18     ` H.J. Lu
2010-04-11 21:12 ` H.J. Lu
2010-04-11 21:18   ` H.J. Lu
2010-04-12  7:46   ` Pedro Alves
2010-04-12 13:05     ` H.J. Lu
2010-04-12 13:26       ` Pedro Alves

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=201004111713.04169.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=hjl.tools@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