[Lldb-commits] [lldb] [lldb] Step over non-lldb breakpoints (PR #174348)

[David Spickett via lldb-commits]

DavidSpickett wrote:

> This might be expected, but building with debug information changes where the breakpoint lands when you issue b main. I didn't expect it at any rate.

I think the debug information allows us to break just after the prologue, rather than the first instruction of the function. If so, that's intended. That's the first line as far as the user is concerned.

You should add a note to the test to say that the position of the breakpoint is deliberately not where I did it my example. Will help anyone who happens to modify the test for some unrelated reason and can't figure out the problem.

> Comparing with an unmodified lldb (version 16), it looks like the behaviour is the same, so it's maybe at least not a regression? I am really not sure how best to try to fix this though, as I don't know why my code isn't being called.

I am inclined to say the same thing. I'll look around the logs just in case there's something really obvious there.

https://github.com/llvm/llvm-project/pull/174348