This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug breakpoints/20739] Badly formatted adress string in error message
- From: "th3c0r1uk at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Sat, 29 Oct 2016 16:19:21 +0000
- Subject: [Bug breakpoints/20739] Badly formatted adress string in error message
- Auto-submitted: auto-generated
- References: <bug-20739-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=20739
th3c0r1uk at gmail dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |th3c0r1uk at gmail dot com
--- Comment #1 from th3c0r1uk at gmail dot com ---
(In reply to ghjghj530-bubu from comment #0)
> GDB 7.10, machine interface
>
> When setting a fast tracepoint at an invalid line the error response is
> badly formatted. The memory address is printed with a 0x0x-prefix instead of
> a simple 0x.
>
> Example:
> &"ftrace C:/projects/xy/Tracepoints/xy.c:26\n"
> &"May not have a fast tracepoint at 0x0x44c0ad8; instruction is only 3 bytes
> long, need at least 5 bytes for the jump\n"
> ^error,msg="May not have a fast tracepoint at 0x0x44c0ad8; instruction is
> only 3 bytes long, need at least 5 bytes for the jump"
>
> Notice the "0x0x44c0ad8"!
>
> Expected behavior: GDB prints only one 0x-prefix.
Reproducible under 7.12. A fix should be fairly simple, tho.
--
You are receiving this mail because:
You are on the CC list for the bug.