public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "yufeng.zhang at arm dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/14531] New: gdb.base/dprintf.exp fails in newlib environment
Date: Thu, 30 Aug 2012 17:31:00 -0000	[thread overview]
Message-ID: <bug-14531-4717@http.sourceware.org/bugzilla/> (raw)

http://sourceware.org/bugzilla/show_bug.cgi?id=14531

             Bug #: 14531
           Summary: gdb.base/dprintf.exp fails in newlib environment
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: testsuite
        AssignedTo: unassigned@sourceware.org
        ReportedBy: yufeng.zhang@arm.com
    Classification: Unclassified


I have seen the following failures in a bare-metal environment with newlib:

set dprintf-function fprintf^M
(gdb) PASS: gdb.base/dprintf.exp: Set dprintf function
set dprintf-channel stderr^M
(gdb) PASS: gdb.base/dprintf.exp: Set dprintf channel
jump *start^M
Line 0 is not in `foo'.  Jump anyway? (y or n) y^M
Continuing at 0x400178.^M
^M
Breakpoint 2, main (argc=1, argv=0x2041bfe0) at
gdb/testsuite/gdb.base/dprintf.c:33^M
33        int loc = 1234;^M
(gdb) continue^M
Continuing.^M
kickoff 1234^M
also to stderr 1234^M
No symbol "stderr" in current context.^M
(gdb) FAIL: gdb.base/dprintf.exp: 1st dprintf, fprintf
continue^M
Continuing.^M
No symbol "stderr" in current context.^M
(gdb) FAIL: gdb.base/dprintf.exp: 2nd dprintf, fprintf
---------------------- CUT ----------------------

The reason of the failure is because that 'stderr' in the newlib has the
following definition:

#ifndef _REENT_ONLY
#define stdin   (_REENT->_stdin)
#define stdout  (_REENT->_stdout)
#define stderr  (_REENT->_stderr)
#else /* _REENT_ONLY */
#define stdin   (_impure_ptr->_stdin)
#define stdout  (_impure_ptr->_stdout)
#define stderr  (_impure_ptr->_stderr)
#endif /* _REENT_ONLY */

while in the GNU/Linux env, there are 'stderr's defined as both the macro and
variable:

/* Standard streams.  */
extern struct _IO_FILE *stdin;          /* Standard input stream.  */
extern struct _IO_FILE *stdout;         /* Standard output stream.  */
extern struct _IO_FILE *stderr;         /* Standard error output stream.  */
#ifdef __STDC__
/* C89/C99 say they're macros.  Make them happy.  */
#define stdin stdin
#define stdout stdout
#define stderr stderr
#endif

This is probably why this test doesn't fail in GNU/Linux but newlib.  I think
we need a more robust way to test 'dprintf' with 'set dprintf-function fprintf'
and 'set dprintf-channel stderr'.  The C standard has specified that 'stderr'
is just a macro.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


             reply	other threads:[~2012-08-30 17:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-30 17:31 yufeng.zhang at arm dot com [this message]
2012-09-08 14:39 ` [Bug testsuite/14531] " qiyao at gcc dot gnu.org
2012-09-10 13:27 ` palves at redhat dot com
2012-09-18  9:49 ` yufeng.zhang at arm dot com

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=bug-14531-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).