Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	        "dje@google.com" <dje@google.com>
Subject: Re: [patch] Fix for gdb.threads/staticthreads.exp failure on Linux
Date: Mon, 22 Jun 2009 20:21:00 -0000	[thread overview]
Message-ID: <8ac60eac0906221321r45c43a13g87a830f8dd3487ea@mail.gmail.com> (raw)
In-Reply-To: <4A3FC8CA.5070700@vmware.com>

On Mon, Jun 22, 2009 at 11:09 AM, Michael Snyder<msnyder@vmware.com> wrote:

> Have you, or could you, run regression testing in i686?

This is glibc-version related, rather than x86_64 vs. i686:

Using glibc-2.7: "runtest gdb.threads/staticthreads.exp" gives:

  # of expected passes            8
  # of known failures             1

in both i686 and x86_64 modes.

But using glibc-2.3.6 (which is my target):

  FAIL: gdb.threads/staticthreads.exp: running to main in runto
  FAIL: gdb.threads/staticthreads.exp: Continue to main's call of sem_post
  FAIL: gdb.threads/staticthreads.exp: handle SIG32 helps

		  === gdb Summary ===

  # of expected passes            6
  # of unexpected failures        3
  # of known failures             1

again in both i686 and x86_64 modes.

Thanks,
-- 
Paul Pluzhnikov


  reply	other threads:[~2009-06-22 20:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-05 22:22 Paul Pluzhnikov
2009-06-15 18:39 ` Paul Pluzhnikov
2009-06-22 16:10   ` Paul Pluzhnikov
2009-06-22 18:10     ` Michael Snyder
2009-06-22 20:21       ` Paul Pluzhnikov [this message]
2009-06-29 14:36         ` Paul Pluzhnikov
2009-07-09  6:36           ` Paul Pluzhnikov
2009-07-16  2:42         ` Doug Evans
2009-07-16  2:43           ` Doug Evans
2009-07-16 20:45           ` Paul Pluzhnikov
2009-07-16 20:54             ` Paul Pluzhnikov
2009-07-16 21:16             ` Doug Evans

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=8ac60eac0906221321r45c43a13g87a830f8dd3487ea@mail.gmail.com \
    --to=ppluzhnikov@google.com \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.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