This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug breakpoints/20739] New: Badly formatted adress string in error message
- From: "ghjghj530-bubu at yahoo dot de" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Thu, 27 Oct 2016 07:05:18 +0000
- Subject: [Bug breakpoints/20739] New: Badly formatted adress string in error message
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=20739
Bug ID: 20739
Summary: Badly formatted adress string in error message
Product: gdb
Version: 7.10
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: breakpoints
Assignee: unassigned at sourceware dot org
Reporter: ghjghj530-bubu at yahoo dot de
Target Milestone: ---
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.
--
You are receiving this mail because:
You are on the CC list for the bug.