http://llvm.org/bugs/show_bug.cgi?id=17096
Bug ID: 17096
Summary: Incorrect stop reason data for multiple breakpoints
Product: lldb
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: All Bugs
Assignee: [email protected]
Reporter: [email protected]
Classification: Unclassified
SBThread.GetStopReasonDataAtIndex() seems to return the wrong data. Consider
the following session:
jowagner@dslabpc6:/tmp$ cat simple.c
#include <stdio.h>
int main() {
printf("Hello, world!\n");
return 0;
}
jowagner@dslabpc6:/tmp$ gcc -Wall -g -o simple simple.c
jowagner@dslabpc6:/tmp$ ./simple
Hello, world!
jowagner@dslabpc6:/tmp$ lldb-3.4 ./simple
Current executable set to './simple' (x86_64).
(lldb) breakpoint set -n main
Breakpoint 1: where = simple`main + 4 at simple.c:4, address =
0x0000000000400590
(lldb) breakpoint set -n main
Breakpoint 2: where = simple`main + 4 at simple.c:4, address =
0x0000000000400590
(lldb) run
Process 5262 launched: './simple' (x86_64)
Process 5262 stopped
* thread #1: tid = 5262, 0x0000000000400590 simple`main + 4 at simple.c:4, name
= 'simple', stop reason = breakpoint 1.1 2.1
frame #0: 0x0000000000400590 simple`main + 4 at simple.c:4
1 #include <stdio.h>
2
3 int main() {
-> 4 printf("Hello, world!\n");
5 return 0;
6 }
(lldb) script
Python Interactive Interpreter. To exit, type 'quit()', 'exit()' or Ctrl-D.
>>> lldb.thread.GetStopReasonDataCount()
4L
>>> lldb.thread.GetStopReasonDataAtIndex(0)
1L
>>> lldb.thread.GetStopReasonDataAtIndex(1)
1L
>>> lldb.thread.GetStopReasonDataAtIndex(2)
1L
>>> lldb.thread.GetStopReasonDataAtIndex(3)
1L
>>> lldb.thread.GetStopReasonDataAtIndex(4)
0L
One can see that the stop reason is displayed correctly in the thread listing,
but that GetStopReasonDataAtIndex(2) returns the wrong value.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
lldb-dev mailing list
[email protected]
http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
