From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: -lmcheck new FAILs for __FILE__ [Re: FYI: fix PR macros/13205]
Date: Sat, 19 May 2012 07:52:00 -0000 [thread overview]
Message-ID: <20120519075208.GA3761@host2.jankratochvil.net> (raw)
In-Reply-To: <87ehqjoopc.fsf@fleche.redhat.com>
On Wed, 16 May 2012 22:28:31 +0200, Tom Tromey wrote:
> Built and regtested on x86-64 Fedora 16.
Getting on x86-64 Fedora 16:
FAIL: gdb.base/macscp.exp: info macro __FILE__ before running
FAIL: gdb.base/macscp.exp: print __FILE__
info macro __FILE__^M
Defined at ./gdb.base/macscp1.c:-1^M
#define __FILE__ "./gdb.base/macscp3.h"<93><93><93><93><93><93><93><93><93><93><93><93><93><93><93><93><93><93>Ã^WÃZ1^M
(gdb) FAIL: gdb.base/macscp.exp: info macro __FILE__ before running
print __FILE__^M
Invalid character '<93>' in expression.^M
(gdb) FAIL: gdb.base/macscp.exp: print __FILE__
It PASSes without -lmcheck.
Thanks,
Jan
next prev parent reply other threads:[~2012-05-19 7:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 20:28 FYI: fix PR macros/13205 Tom Tromey
2012-05-16 20:43 ` Pedro Alves
2012-05-16 20:44 ` Tom Tromey
2012-05-19 7:52 ` Jan Kratochvil [this message]
2012-05-21 15:27 ` -lmcheck new FAILs for __FILE__ [Re: FYI: fix PR macros/13205] Tom Tromey
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=20120519075208.GA3761@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--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