mihail.nistor at freescale dot com
2015-03-19 11:08:05 UTC
https://sourceware.org/bugzilla/show_bug.cgi?id=18144
Bug ID: 18144
Summary: the skip prologue functionality doesn't work well for
same assembly functions
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: tdep
Assignee: unassigned at sourceware dot org
Reporter: mihail.nistor at freescale dot com
Created attachment 8198
--> https://sourceware.org/bugzilla/attachment.cgi?id=8198&action=edit
an example, gdb and gcc information
The gdb always sets the break-point to an assembly function (or a symbol) at
the next line when the ASM file is compiled with debug information (-g option)
even if the function does not have prologue instructions.
Let's have an example:
.global _start
_start:
nop
nop
ret
The gdb will put the break-point at the second nop instruction - that is wrong
- when the user uses the break-point _start command.
In this scenario, the gdb should put the break-point at the first nop
instruction.
Bug ID: 18144
Summary: the skip prologue functionality doesn't work well for
same assembly functions
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: tdep
Assignee: unassigned at sourceware dot org
Reporter: mihail.nistor at freescale dot com
Created attachment 8198
--> https://sourceware.org/bugzilla/attachment.cgi?id=8198&action=edit
an example, gdb and gcc information
The gdb always sets the break-point to an assembly function (or a symbol) at
the next line when the ASM file is compiled with debug information (-g option)
even if the function does not have prologue instructions.
Let's have an example:
.global _start
_start:
nop
nop
ret
The gdb will put the break-point at the second nop instruction - that is wrong
- when the user uses the break-point _start command.
In this scenario, the gdb should put the break-point at the first nop
instruction.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are receiving this mail because:
You are on the CC list for the bug.