Yes, it would. But anything that would change the breakpoint size dynamically would have to set m_breakpoint_pc_offset (probably to 0, the default) and manipulate the PC in target dependent code. It wouldn’t be able to use this change, but wouldn’t be hurt by it.
From: Todd Fiala [mailto:[email protected]] Sent: Thursday, June 05, 2014 4:00 PM To: Ted Woodward Cc: [email protected] Subject: Re: [lldb-dev] qHostInfo proposal to add breakpoint pc offset Might that value be dependent on the type of code that is getting executed? (e.g. ARM thumb vs. ARM32)? IOW is it really stable for a given host? On Thu, Jun 5, 2014 at 1:49 PM, Ted Woodward <[email protected]> wrote: On some architectures, when a breakpoint is hit, the PC is set to a different value and needs to be adjusted. This is handled in ProcesGDBRemote.cpp by the variable m_breakpoint_pc_offset. The problem is this variable is only set via a python target definition file. I propose extending qHostInfo to add bp_pc_decr:<offset>. m_breakpoint_pc_offset would be set to this signed integer. Ted _______________________________________________ lldb-dev mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev -- Todd Fiala | Software Engineer | <mailto:[email protected]> [email protected] | 650-943-3180
_______________________________________________ lldb-dev mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
