[Lldb-commits] [PATCH] D108061: [lldb] Add support for shared library load when executable called through ld.

Greg Clayton via Phabricator via lldb-commits lldb-commits at lists.llvm.org
Tue Aug 17 17:34:03 PDT 2021


clayborg added a comment.

In D108061#2950858 <https://reviews.llvm.org/D108061#2950858>, @rdhindsa wrote:

> Updated the test to check for the respective function name from the shared library in the frames.
> I didn't add run_to_source_breakpoint since we can't set a breakpoint on main initially before running the program.  
> Hence it would need to be run first and then we can check later to see if the function name is available. Please let me know if you think there is any concern with this way.

We need to figure out where the main program is loaded somehow and the dynamic loader needs to set the load address for "a.out" so that breakpoints can be resolved and hit. We _do_ need to make sure a breakpoint can be set and hit otherwise this patch will just show us a debug session that has the dynamic loader as the main executable, but we will never see where the program it will run is loaded. That is the tricky part of this patch and where I got stuck. GDB is able to do this, but I didn't look at how they did it. We will want our program to show up in the "image list" output with a valid load address.

Are you able to hit a breakpoint if one is set in the a.out program?


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D108061/new/

https://reviews.llvm.org/D108061



More information about the lldb-commits mailing list