public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "xdegaye at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug mi/13170] New: some :werror and warning messages are written to gdb/mi log stream
Date: Thu, 08 Sep 2011 19:34:00 -0000	[thread overview]
Message-ID: <bug-13170-4717@http.sourceware.org/bugzilla/> (raw)

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

             Bug #: 13170
           Summary: some :werror and warning messages are written to
                    gdb/mi log stream
           Product: gdb
           Version: 7.3
            Status: NEW
          Severity: normal
          Priority: P2
         Component: mi
        AssignedTo: unassigned@sourceware.org
        ReportedBy: xdegaye@gmail.com
    Classification: Unclassified


How-To-Repeat
-------------

* build a plain executable:

$ echo "main(){}" | gcc -x c -g  -


* run the following test and confirm that the message "No source file
  named foo.c." is written to gdb/mi log stream instead of the console
  stream:

$ gdb --interpreter=mi -q -ex "set confirm off" a.out
=thread-group-added,id="i1"
~"Reading symbols from /home/xavier/tmp/a.out..."
~"done.\n"
(gdb)
-interpreter-exec console "break foo.c:1"
&"No source file named foo.c.\n"
^done
(gdb)
quit
&"quit\n"

-- 
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:[~2011-09-08 19:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-08 19:34 xdegaye at gmail dot com [this message]
2011-09-08 20:43 ` [Bug mi/13170] some error " xdegaye at gmail dot com
2011-09-08 20:52 ` xdegaye at gmail 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-13170-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).