Hi Sasha,
Sorry for the late reply.
On Thu, 2019-09-12 at 15:22 +, Sasha Da Rocha Pinheiro wrote:
> For my knowledge about it, this information is not encoded in the
> dwarf_line state machine instructions. Right? Would you know how to
> get it?
>
> I know that the state machine will shift l
src(line, NULL, NULL);
status = dwarf_lineaddr(line, ¤t_statement.start_addr);
// here add line info to our own structure
}
In the previous email I gave you an example for the line 233, which gdb adds
two breakpoints in two different functions. I understand that, because
optimizations
Hi Sasha,
On Wed, Sep 11, 2019 at 09:52:23PM +, Sasha Da Rocha Pinheiro wrote:
> how do we get the line info range end address for a given line and file?
I am not sure I understand your question competely. What are you
using to get at the line and file? In theory there is no "r
Hi all,
how do we get the line info range end address for a given line and file?
For instance, gdb adds 2 breapoint to:
(gdb) b /g/g90/devkota1/LULESH/lulesh.cc:233
Breakpoint 1 at 0x4060a0: /g/g90/devkota1/LULESH/lulesh.cc:233. (2 locations)
(gdb) i b
Num Type Disp Enb Address
