public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "asmwarrior at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug mi/16868] Wrong escaping of "script" in breakpoint-created event
Date: Thu, 24 Apr 2014 14:48:00 -0000 [thread overview]
Message-ID: <bug-16868-4717-ymsnJUptzk@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16868-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16868
--- Comment #4 from asmwarrior <asmwarrior at gmail dot com> ---
(In reply to Simon Marchi from comment #3)
> asmwarrior, you are right, it is the same bug. It happens many times in MI
> async events. Is it possible to rename your bug to make it more generic?
> Then we can mark this one as duplicate.
>
> Two other examples:
>
> =breakpoint-modified,bkpt={number="1",type="breakpoint",disp="keep",
> enabled="y",addr="0x0000000000400a29",func="main",file="test.c",fullname="/
> home/simark/src/test.c",line="55",thread-groups=["i1"],times="0",
> script={"echo hey\\"you"},original-location="main"}
> =cmd-param-changed,param="prompt",value="\\"tourlou\\""
Hi, Simon, good suggestion.
Every one can change the bug title, so if you have a better name for the
general bug, you can directly edit that bug title.
I have debugged that bug a little, you can see some of my analysis in that
bug's comments, GDB should have a state variable for the out put stream, so if
it backslash is already doubled, we won't double it for the next stream copy.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2014-04-24 14:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-23 19:40 [Bug mi/16868] New: " simon.marchi at ericsson dot com
2014-04-24 3:42 ` [Bug mi/16868] " asmwarrior at gmail dot com
2014-04-24 3:44 ` asmwarrior at gmail dot com
2014-04-24 14:37 ` simon.marchi at ericsson dot com
2014-04-24 14:48 ` asmwarrior at gmail dot com [this message]
2014-04-24 15:28 ` simon.marchi at ericsson 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-16868-4717-ymsnJUptzk@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).