[Bug testsuite/14531] gdb.base/dprintf.exp fails in newlib environment

["qiyao at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>]

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

Yao Qi <qiyao at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |qiyao at gcc dot gnu.org

--- Comment #1 from Yao Qi <qiyao at gcc dot gnu.org> 2012-09-08 14:39:26 UTC ---
(In reply to comment #0)
> 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

I'd like to treat it as an incompleteness of test case here.  IMO, command 'set
dprintf-channel' gives user the freedom to set the right channel to display
messages, so the user has to set the right channel.

The test should be smart to enough to 'set dprintf-channel' correctly if
'stderr' doesn't exist at all.

Maybe we can do 'set dprintf-channel _impure_ptr->_stderr' for newlib??

-- 
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.