xNejX
asked on
find our where the exe is being aborted with abort()
Hi,
My c++ is getting gets an error when under the MTD and it just exits when it is built under MT. In MTD i get this error:
I can choose to ignore it, cancel it or retry but they all lead to the exe getting closed. I gues that abort() is being called somewhere but i've been looking and searching for it and I cant find it. It is probably not in my code but a result when communicating with a socket while the internet connection goes down.
Is there a way that I can find out where this error is being called from (line and file)?
Thank you
My c++ is getting gets an error when under the MTD and it just exits when it is built under MT. In MTD i get this error:
"Debug Error!
R6010
- abort() has been called
(Press Retry to debug the application)"
I can choose to ignore it, cancel it or retry but they all lead to the exe getting closed. I gues that abort() is being called somewhere but i've been looking and searching for it and I cant find it. It is probably not in my code but a result when communicating with a socket while the internet connection goes down.
Is there a way that I can find out where this error is being called from (line and file)?
Thank you
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
i will try the second solution, the retry doesn't do anything
You could also try to to rund your aqpp in the debugger from the start, it should then stop on the line with the 'abort()'.
ASKER
I tried to do it with the callstack but as soon as it aborts the callstact window dissapears from Visual Studio and when I reopen it it is empty.
All that I can get from the "Output" window in visual studio is The program '[22476] Unasl.exe: Native' has exited with code 1 (0x1).
How do i rund my aqpp?
All that I can get from the "Output" window in visual studio is The program '[22476] Unasl.exe: Native' has exited with code 1 (0x1).
How do i rund my aqpp?
Hmm, can you try to set a breakpoint on 'abort()'? Press CTRL+B and enter 'abort' in the text field.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
@jkr
Do you know the shortcut or the function name in VS 2010? CTRL + B doesn't do anything => { (Ctrl+B) was pressed. Waiting for second key or chord... }?
Do you know the shortcut or the function name in VS 2010? CTRL + B doesn't do anything => { (Ctrl+B) was pressed. Waiting for second key or chord... }?
Try "Debug|New Breakpoint|Break at Function..."
ASKER
was i supposed to put a certain line number and char, should i put in abort or abort()?
cause it didn't break on anything...
cause it didn't break on anything...
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
>>and file)?
Yes - "Press Retry to debug the application" (pardon the pun) and examine the call stack. This will lead you to the file and line in your code that subsequently caused 'abort()' to be called.