Skip to main content
Software Engineering

Return to Question

Post Closed as "Needs more focus" by user53019, gnat, user40980, user22815, Bart van Ingen Schenau
Removed fluff, made question less of an opinion poll and more focused.
Source Link
user22815
user22815

Reasons that debug Debug symbols could change the application execution

The motivation for this question is that I'm in a situation in which I have to set up remote debugging for a multi threaded application running on a embedded device. C++ is the language.

I've gotten so far and got the remote debugging working for a simple application, but when applying the same procedures on the multi threaded giant just don't work (the application starts behaving unpredictably when built with debug). There was no stopping of the execution (no breakpoints), just a continuous standard run, just with debug symbols.

IWhat would like to hear explanations on the different running environments (debug vs stripped) and possible causes forcause a failure in debug mode in this environment? (once again, no breakpoints in debug mode, just continuous running).

Reasons that debug symbols could change the application execution

The motivation for this question is that I'm in a situation in which I have to set up remote debugging for a multi threaded application running on a embedded device. C++ is the language.

I've gotten so far and got the remote debugging working for a simple application, but when applying the same procedures on the multi threaded giant just don't work (the application starts behaving unpredictably when built with debug). There was no stopping of the execution (no breakpoints), just a continuous standard run, just with debug symbols.

I would like to hear explanations on the different running environments (debug vs stripped) and possible causes for a failure in debug mode (once again, no breakpoints in debug mode, just continuous running).

Debug symbols change application execution

I have to set up remote debugging for a multi threaded application running on a embedded device. C++ is the language.

I've gotten so far and got the remote debugging working for a simple application, but when applying the same procedures on the multi threaded giant just don't work (the application starts behaving unpredictably when built with debug). There was no stopping of the execution (no breakpoints), just a continuous standard run, just with debug symbols.

What would cause a failure in debug mode in this environment? (once again, no breakpoints in debug mode, just continuous running)

Source Link
TheMeaningfulEngineer
TheMeaningfulEngineer
  • 961
  • 2
  • 10
  • 17

Reasons that debug symbols could change the application execution

The motivation for this question is that I'm in a situation in which I have to set up remote debugging for a multi threaded application running on a embedded device. C++ is the language.

I've gotten so far and got the remote debugging working for a simple application, but when applying the same procedures on the multi threaded giant just don't work (the application starts behaving unpredictably when built with debug). There was no stopping of the execution (no breakpoints), just a continuous standard run, just with debug symbols.

I would like to hear explanations on the different running environments (debug vs stripped) and possible causes for a failure in debug mode (once again, no breakpoints in debug mode, just continuous running).