Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Fernando Nasser <fnasser@redhat.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: drow@mvista.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA/testsuite] Test printing complex numbers in C
Date: Wed, 04 Dec 2002 15:19:00 -0000	[thread overview]
Message-ID: <3DEE8D97.4080703@redhat.com> (raw)
In-Reply-To: <200212031654.gB3GsZL31271@duracef.shout.net>

Thanks Michael.  Nice to have you back!

Michael Elizabeth Chastain wrote:> 		  stabs           DWARF-2
>   GCC 2.95        pass            fail
>   GCC 3.x         fail            pass
> 
> Do gcc 2.95.3/dwarf-2 and gcc 3.x/stabs+ have identical output,
> or different output?
> 
> If they are different output, you can do:
> 
>   send_gdb "blah"
>   gdb_expect {
>     -re "good output" {
>       pass ...
>     }
>     -re "flaky gcc 2.95.3/dwarf-2 output" {
>       setup_xfail_format "dwarf-2"
>       fail ...
>     }
>     -re "flaky gcc 3.x/stabs+ output" {
>       setup_xfail_format "stabs+"
>       fail ...
>     }
>     -re ".*" {
>       fail ...
>     }
>   }
> 
> You can also dynamically poke at the executable to see what gcc compiled
> it.  See "probe_demangler" in gdb.c++/cplusfuncs.exp for one way to do it.
> 
> Michael C
> 



-- 
Fernando Nasser
Red Hat - Toronto                       E-Mail:  fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario   M4P 2C9


  reply	other threads:[~2002-12-04 23:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-03  8:54 Michael Elizabeth Chastain
2002-12-04 15:19 ` Fernando Nasser [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-04 20:29 Michael Elizabeth Chastain
2002-10-04 20:21 Daniel Jacobowitz
2002-12-03  8:24 ` Fernando Nasser
2002-12-03  8:33   ` Daniel Jacobowitz
2002-12-04 15:23     ` Fernando Nasser
2002-12-05  7:10 ` Fernando Nasser

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=3DEE8D97.4080703@redhat.com \
    --to=fnasser@redhat.com \
    --cc=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec@shout.net \
    /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