Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Denis PILAT <denis.pilat@st.com>
To: gdb-patches@sourceware.org
Subject: [testsuite] gdb.base/maint.exp errors
Date: Thu, 20 Jul 2006 10:43:00 -0000	[thread overview]
Message-ID: <44BF5E36.9050002@st.com> (raw)

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've patched my maint.exp file to remove them but it isnt worth sending 
this patch if you don't get these errors.

Denis


             reply	other threads:[~2006-07-20 10:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-20 10:43 Denis PILAT [this message]
2006-07-20 13:24 ` Daniel Jacobowitz

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=44BF5E36.9050002@st.com \
    --to=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