• Hipreme (7/7) Jul 10 2022 I'm stuck in a racing condition right now and I'm unable to run a
• z (8/16) Jul 10 2022 Maybe it will work with an external debugger like x96dbg? With
• Kagamin (3/6) Jul 12 2022 Open the threads window and click on threads there, their stack

Hipreme <msnmancini hotmail.com> writes:

I'm stuck in a racing condition right now and I'm unable to run a 
debugger on the code. Usually I was using Visual Studio 2019 for 
debugging my code, but it shows the following message:

"Your app has entered a break state, but there is no code to show 
because all threads were executing external code (typically 
system or framework code)."

I can only access the main thread code which stops on my semaphore

z <z z.com> writes:

On Sunday, 10 July 2022 at 21:27:08 UTC, Hipreme wrote:
 I'm stuck in a racing condition right now and I'm unable to run 
 a debugger on the code. Usually I was using Visual Studio 2019 
 for debugging my code, but it shows the following message:

 "Your app has entered a break state, but there is no code to 
 show because all threads were executing external code 
 (typically system or framework code)."

 I can only access the main thread code which stops on my 
 semaphore

Maybe it will work with an external debugger like x96dbg? With 
debug symbols(i'd recommend LDC build too) it should be able to 
show threads and where in the code it was stuck in(i'm assuming 
each thread will be stuck in a wait loop)
It's also possible the error message is just the truth, but it 
seems weird that it can't at least display the call stack in that 
case.

Kagamin <spam here.lot> writes:

On Sunday, 10 July 2022 at 21:27:08 UTC, Hipreme wrote:
 "Your app has entered a break state, but there is no code to 
 show because all threads were executing external code 
 (typically system or framework code)."

Open the threads window and click on threads there, their stack 
will be in the stack window.