From: Daniel Jacobowitz <drow@false.org>
To: Denis PILAT <denis.pilat@st.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [testsuite] gdb.base/maint.exp errors
Date: Thu, 20 Jul 2006 13:24:00 -0000 [thread overview]
Message-ID: <20060720132359.GA16437@nevyn.them.org> (raw)
In-Reply-To: <44BF5E36.9050002@st.com>
On Thu, Jul 20, 2006 at 12:43:02PM +0200, Denis PILAT wrote:
> I get some errors while running maint.exp with the gdb6.5 on linux RHEL3.0:
> FAIL: gdb.base/maint.exp: maint print psymbols
> FAIL: gdb.base/maint.exp: maint print msymbols
> FAIL: gdb.base/maint.exp: maint print msymbols
> FAIL: gdb.base/maint.exp: maint print symbols
>
> These errors come from the "shell ls" command that tests presence od
> output files, this command emits some strange character before the gdb
> prompt and the catching rule in the .exp file is not matched. I'm afraid
> it could come from my environment.
>
> Do you guys get these error as well or does it come from my environment ?
I don't think I've ever seen this before.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2006-07-20 13:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-20 10:43 Denis PILAT
2006-07-20 13:24 ` Daniel Jacobowitz [this message]
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=20060720132359.GA16437@nevyn.them.org \
--to=drow@false.org \
--cc=denis.pilat@st.com \
--cc=gdb-patches@sourceware.org \
/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