kwk marked an inline comment as done. kwk added a comment. labath, please see my answer to your question and maybe help me out why you think I don't test what I want to test.
================ Comment at: lldb/lit/Breakpoint/minidebuginfo-set-and-hit-breakpoint.test:50 + +# RUN: LD_LIBRARY_PATH=$LD_LIBRARY_PATH:%T %lldb -x -b -o 'b multiplyByThree' -o 'b multiplyByFour' -o 'breakpoint list -v' -o 'run' -o 'continue' %t.binary | FileCheck %s + ---------------- labath wrote: > Instead of messing with the environment, it might be better to just set the > rpath (`-Wl,-rpath`) of the executable appropriately (but I would still like > to know what you're exactly trying to test with that extra shared library). labath, I'd like to test the following scenario: Set a breakpoint on a symbol (`multiplyByThree`) in the `.dynsym` section and one on a symbol (`multiplyByFour`) from the .`symtab` that's embedded within the `.gnu_debugdata` section. I have no clue how to get those symbols without using a shared lib. Do you? Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D66791/new/ https://reviews.llvm.org/D66791 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
