- User Since
- Jul 28 2017, 5:31 AM (115 w, 4 d)
Apr 30 2018
Apr 16 2018
Thank you for bearing with me. This looks fine to me now, but I think Greg or Jim should take one more look at the final result.
Apr 11 2018
Cheking target architecture to run ppc64-call-functtion.test
Apr 10 2018
Apr 9 2018
- Added assembly test case with debug information.
- Modified refactor of breakpoint address calculation.
Apr 6 2018
Apr 5 2018
Apr 4 2018
- Added test case in lldb-test breakpoint.
- Code refactored and ComputeBreakpointAddress function created.
- Created function to calculate breakpoint address.
- Added test case in lldb-test
Apr 2 2018
I have added a new test case inside the TestMiBreak.py which is the file where we found the issue, and using the LLDB-mi I can disable the skip prologue, where the code can be tested.
Modified as requested and added a new test case.
Mar 27 2018
Mar 20 2018
Yes, I'm running Linux and this test was not working for me, so as discussion above, it was separated to be executed on non Linux and Windows, but the variable number got wrong. Sorry for that.
@davide Let me know if you need that I change it on my diff or any other help.
@davide, I think the error is the variable number, as this is the only command in the test case, could you just change from
@davide Are you sure this is the correct patch? This one was not merged yet.
Could you give more details about the issue? Is it related with one of our changes?
Mar 16 2018
@labath Could you please commit this change?
Mar 14 2018
I would remove all of the "need_adjust_break_address" and just always call that function in the architecture? Or only call it if m_skip_prologue is true? Seems like this logic should always happen. Seems like magic to only adjust the breakpoint address if the prologue byte size is zero or we aren't skipping the prologue. Feel free to pass any extra args down into AdjustBreakpointAddress() if needed (like m_skip_prologue or prologue_byte_size).
Mar 13 2018
Mar 6 2018
Reverted changes of
If you need to force something to use a global entry point you might be able to switch this test to use a shared library that contains that function. This would then require that the global entry point is used?
However, this looks like a different story. I don't think that whoever created the skip-prologue option even knew local entry points exist, but I think he would be surprised by the behavior you have here. And I am certain that I, as a user, would be very surprised (and upset) if setting skip-prologue=false would cause my breakpoints to not get hit in some (not so infrequent) conditions. So in light of the different entry points on ppc, I think we should read the "skip-prologue" option as "stop as early as possible" (while still making sure that you stop!), and treat this as a bug and not something that should be hacked around.
About the environ symbol issue, I'm going to move to a separate test method in the same test file, is it ok?
Mar 5 2018
Dec 14 2017
Dec 11 2017
@nemanjai, I still don't have permissions for committing, so could you commit this?
Dec 6 2017
Moving flag set to parent