Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: "Pierre Muller" <muller@ics.u-strasbg.fr>
Subject: Re: [RFA] fix win32-nat failure
Date: Thu, 02 Oct 2008 13:02:00 -0000	[thread overview]
Message-ID: <200810021401.20466.pedro@codesourcery.com> (raw)
In-Reply-To: <00b701c92485$8bc23260$a3469720$@u-strasbg.fr>

On Thursday 02 October 2008 12:53:44, Pierre Muller wrote:
> I ran a testsuite on cygwin with the patch below,
> I got this results:
> 
>                 === gdb Summary ===
> 
> # of expected passes            11190
> # of unexpected failures        469
> # of expected failures          58
> # of unknown successes          2
> # of known failures             110
> # of unresolved testcases       40
> # of untested testcases         15
> # of unsupported tests          23
> /usr/local/src/gdbcvs/build-bare/gdb/testsuite/../../gdb/gdb version
> 6.8.50.200
> 81002-cvs -nx
> 
> This seems like a "normal" outcome for cygwin native gdb.

Hmmm, I don't have a good baseline stored to compare this to, but, from
memory, this looks worse than is was a few weeks ago...  The failure count
should be much lower currently, due to both the fix that forced unbuffered
stdout on Cygwin, and the skip __main fix.

Oh, I'm running the testsuite too, and I'm getting several crashes
like these, which I had never seen before:

 $ ./gdb /home/pedro/gdb/baseline/build/gdb/testsuite/gdb.cp/class2
 GNU gdb (GDB) 6.8.50.20081002-cvs
 Copyright (C) 2008 Free Software Foundation, Inc.
 License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
 This is free software: you are free to change and redistribute it.
 There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
 and "show warranty" for details.
 This GDB was configured as "i686-pc-cygwin".
 For bug reporting instructions, please see:
 <http://www.gnu.org/software/gdb/bugs/>...
 BFD: BFD (GNU Binutils) 2.19.50.20081002 internal error, aborting at ../../src/bfd/coffcode.h line 842 in handle_COMDAT

 BFD: Please report this bug.

This is with stock gcc and binutils.  Looks like something
broke recently on the binutils/bfd side...

> Thus I would like to get approval for the following patch,
> ChangeLog entry:
> 
> 2008-10-02  Pierre Muller  <muller@ics.u-strasbg.fr>
> 		Pedro Alves  <pedro@codesourcery.com>
> 
> 	* win32-nat.c (do_initial_win32_stuff): Set inferior_ptid.

We're doing a small adjustment that I should have made myself,
due to new core expectations, so I don't think we don't need to
bother Christopher with this one.

OK.  Please check it in.

Thanks!

-- 
Pedro Alves


  reply	other threads:[~2008-10-02 13:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-01 12:25 [RFC] " Pierre Muller
2008-10-01 12:50 ` Pedro Alves
2008-10-01 18:10 ` Pedro Alves
2008-10-02  8:41   ` Pierre Muller
2008-10-02 11:58     ` [RFA] " Pierre Muller
2008-10-02 13:02       ` Pedro Alves [this message]
2008-10-02 14:22         ` Pierre Muller
2008-10-02 15:25         ` Christopher Faylor
2008-10-02 15:54           ` Pedro Alves
2008-10-02 19:07             ` Christopher Faylor
2008-10-02 12:12     ` [RFC] " 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=200810021401.20466.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=muller@ics.u-strasbg.fr \
    /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