71c4da83b6
For instance, some recent clang emits this code on x86_64:
0x100002b99 <+57>: callq 0x100002b40 ; step_out_of_here at main.cpp:11
-> 0x100002b9e <+62>: xorl %eax, %eax
0x100002ba0 <+64>: popq %rbp
0x100002ba1 <+65>: retq
and the "xorl %eax, %eax" is attributed to the same line as the callq. Since
step out is supposed to stop just on returning from the function, you can't guarantee
it will end up on the next line. I changed the test to check that we were either
on the call line or on the next line, since either would be right depending on the
debug information.
43 lines
892 B
C++
43 lines
892 B
C++
// This test is intended to create a situation in which two threads are stopped
|
|
// at a breakpoint and the debugger issues a step-out command.
|
|
|
|
#include "pseudo_barrier.h"
|
|
#include <thread>
|
|
|
|
pseudo_barrier_t g_barrier;
|
|
|
|
volatile int g_test = 0;
|
|
|
|
void step_out_of_here() {
|
|
g_test += 5; // Set breakpoint here
|
|
}
|
|
|
|
void *
|
|
thread_func ()
|
|
{
|
|
// Wait until both threads are running
|
|
pseudo_barrier_wait(g_barrier);
|
|
|
|
// Do something
|
|
step_out_of_here(); // But we might still be here
|
|
|
|
// Return
|
|
return NULL; // Expect to stop here after step-out.
|
|
}
|
|
|
|
int main ()
|
|
{
|
|
// Don't let either thread do anything until they're both ready.
|
|
pseudo_barrier_init(g_barrier, 2);
|
|
|
|
// Create two threads
|
|
std::thread thread_1(thread_func);
|
|
std::thread thread_2(thread_func);
|
|
|
|
// Wait for the threads to finish
|
|
thread_1.join();
|
|
thread_2.join();
|
|
|
|
return 0;
|
|
}
|