From: Michael Snyder <msnyder@vmware.com>
To: Tom Tromey <tromey@redhat.com>,
Pierre Muller <muller@ics.u-strasbg.fr>,
gdb-patches@sourceware.org
Subject: Re: Results of macscp.exp test on cygwin
Date: Thu, 09 Oct 2008 20:21:00 -0000 [thread overview]
Message-ID: <48EE6707.3050401@vmware.com> (raw)
In-Reply-To: <20081009181350.GA15369@caradoc.them.org>
Daniel Jacobowitz wrote:
> On Thu, Oct 09, 2008 at 10:27:07AM -0600, Tom Tromey wrote:
>>>>>>> "Pierre" == Pierre Muller <muller@ics.u-strasbg.fr> writes:
>> Pierre> Shouldn't we force dwarf-2 debug format, or at least
>> Pierre> skip the test if only stabs format is available?
>>
>> Seems like a decent idea to me.
>
> Yes; I suggest skipping, rather than forcing. There should be some
> examples of this in the testsuite already.
Regarding macscp.exp, I am running it on RHEL-4 and seeing
the majority of tests fail.
bash-3.00$ gcc --version
gcc (GCC) 3.4.6 20060404 (Red Hat 3.4.6-9)
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
next prev parent reply other threads:[~2008-10-09 20:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-09 11:37 Pierre Muller
2008-10-09 16:29 ` Tom Tromey
2008-10-09 16:46 ` Pedro Alves
2008-10-09 18:14 ` Daniel Jacobowitz
2008-10-09 20:21 ` Michael Snyder [this message]
2008-10-09 22:28 ` Paul Pluzhnikov
2008-10-10 16:04 ` [RFC] " Pierre Muller
2009-01-26 9:13 ` [PING] " Pierre Muller
2009-01-28 13:32 ` [RFC] Use untested for macscp.exp if no macro information generated Pierre Muller
2009-02-01 18:28 ` Daniel Jacobowitz
2009-02-03 14:36 ` [RFC-v2] " Pierre Muller
2009-02-18 22:59 ` [PING] " Pierre Muller
2009-02-19 8:20 ` Tom Tromey
2009-02-20 10:08 ` Pierre Muller
2009-05-11 11:30 ` PING : " Pierre Muller
2009-05-29 23:40 ` Tom Tromey
2009-05-30 8:04 ` Pierre Muller
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=48EE6707.3050401@vmware.com \
--to=msnyder@vmware.com \
--cc=gdb-patches@sourceware.org \
--cc=muller@ics.u-strasbg.fr \
--cc=tromey@redhat.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