diff options
| author | Pedro Alves <pedro@palves.net> | 2022-05-12 20:20:03 +0100 |
|---|---|---|
| committer | Pedro Alves <pedro@palves.net> | 2022-05-20 20:41:02 +0100 |
| commit | 7ab979957c6dd6fddd86b396e9e885ec09002e8e (patch) | |
| tree | ccbbd6ee022099242dd180c3c98ed8f993fe1ccc /gdb/testsuite/gdb.cp | |
| parent | f9703051465a03bace3cc17b80fcd12c19a60821 (diff) | |
| download | gdb-7ab979957c6dd6fddd86b396e9e885ec09002e8e.zip gdb-7ab979957c6dd6fddd86b396e9e885ec09002e8e.tar.gz gdb-7ab979957c6dd6fddd86b396e9e885ec09002e8e.tar.bz2 | |
Make sure momentary breakpoints are always thread-specific
This adds a new ctor to momentary_breakpoints with a few parameters
that are always necessary for momentary breakpoints.
In particular, I noticed that set_std_terminate_breakpoint doesn't
make the breakpoint be thread specific, which looks like a bug to me.
The point of that breakpoint is to intercept std::terminate calls that
happen as result of the called thread throwing an exception that won't
be caught by the dummy frame. If some other thread calls
std::terminate, IMO, it's no different from some other thread calling
exit/_exit, for example.
Change-Id: Ifc5ff4a6d6e58b8c4854d00b86725382d38a1a02
Diffstat (limited to 'gdb/testsuite/gdb.cp')
0 files changed, 0 insertions, 0 deletions