Home/ Questions/Q 8636249
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-12T10:11:06+00:00

I am trying to track the source of a std::exception, in basic_string::erase, I wrapped

  • 0

I am trying to track the source of a std::exception, in basic_string::erase, I wrapped all the locations where I am calling erase directly in try/catch and am not seeing any of these catch blocks be hit, so it must be being called internally from another basic_string method. The exception appears to be the result of a race condition in the code i am working with, so it is very difficult to reproduce, any thoughts on how I could detect and or get a stack trace from this exception? btw this is c++ code on an x86 linux box.

Thank you

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You should try

    (gdb) catch throw

    Then gdb will trigger breakpoint each time exception is thrown. You’ll see a callstack.

    EDIT: This post is a good bunch of tricks for debugging exceptions: GDB: How to break when a specific exception type is thrown?

    • 0