Debug Assertion Failed
-
Hello! Which line of "your" code is triggering this assertion?
It is a crappy thing, but it's life -^ Carlo Pallini
That's a problem Subramanian ji. When i go through Debug then i han't got assertion and when i go through normal mode then i got some time this assertion.This assertion not come regullar.So i han't got exact line of code.If it is possible then help me
-
Provide only the code that has relevance with this issue and take your time to align the code properly. Also, what is
tr,finalstring, etc.,? There's a globaltr(I don't see it declared anywhere) and anothertrinside your worker thread function code with local scope. A perfect recipe for disaster. This is one rare case where I'm going to encourage cross-posting. You may kindly cross-post your code at the coding horror forum too.It is a crappy thing, but it's life -^ Carlo Pallini
Rajesh R Subramanian wrote:
This is one rare case where I'm going to encourage cross-posting. You may kindly cross-post your code at the coding horror forum too.
:laugh:
Cédric Moonen Software developer
Charting control [v2.0] OpenGL game tutorial in C++ -
Yes tr, finalstring both are globle. Worker thread it's not tr it is tt.So sorry for that.
It's better if you can try out sample application with minimum code including function that cause the error that will help you to get into exact problem. And it will also helps others to find out exact cause of problem and to give appropriate solution.
-
That's a problem Subramanian ji. When i go through Debug then i han't got assertion and when i go through normal mode then i got some time this assertion.This assertion not come regullar.So i han't got exact line of code.If it is possible then help me
Try different test cases and narrow down the number of cases for which the crash is occurring. You might as well output text to the debugger window from within your code (if you are not running under the VS debugger, you can still use an external debugger[^] (just connect it to the local machine) and use something like OutputDebugString[^] to print to the debugger). The actual problem might be something as trivial as writing to a pointer that has been released, accessing memory that you don't own, etc., But you need to locate it first.
It is a crappy thing, but it's life -^ Carlo Pallini
-
Try different test cases and narrow down the number of cases for which the crash is occurring. You might as well output text to the debugger window from within your code (if you are not running under the VS debugger, you can still use an external debugger[^] (just connect it to the local machine) and use something like OutputDebugString[^] to print to the debugger). The actual problem might be something as trivial as writing to a pointer that has been released, accessing memory that you don't own, etc., But you need to locate it first.
It is a crappy thing, but it's life -^ Carlo Pallini
-
Try different test cases and narrow down the number of cases for which the crash is occurring. You might as well output text to the debugger window from within your code (if you are not running under the VS debugger, you can still use an external debugger[^] (just connect it to the local machine) and use something like OutputDebugString[^] to print to the debugger). The actual problem might be something as trivial as writing to a pointer that has been released, accessing memory that you don't own, etc., But you need to locate it first.
It is a crappy thing, but it's life -^ Carlo Pallini
-
Hi All how to solve this Debug.
unhandled exception at 0x00541ccf in Test.exe:0xC0000005;Access vilolation reading location 0xfeeefeee
Plz help me
An assertion is completely different than an exception. So which is it?
"Old age is like a bank account. You withdraw later in life what you have deposited along the way." - Unknown
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
-
Hi All how to solve this Debug.
unhandled exception at 0x00541ccf in Test.exe:0xC0000005;Access vilolation reading location 0xfeeefeee
Plz help me
Davitor wrote:
Access vilolation reading location 0xfeeefeee
0xfeeefeee is a Magic Number[^] which has a meaning. This essentially means that you are trying to access memory AFTER it has been freed. You should begin debugging by checking the variables that you are accessing in your worker thread. Best Wishes, -David Delaune
-
Hi All how to solve this Debug.
unhandled exception at 0x00541ccf in Test.exe:0xC0000005;Access vilolation reading location 0xfeeefeee
Plz help me
-
Provide only the code that has relevance with this issue and take your time to align the code properly. Also, what is
tr,finalstring, etc.,? There's a globaltr(I don't see it declared anywhere) and anothertrinside your worker thread function code with local scope. A perfect recipe for disaster. This is one rare case where I'm going to encourage cross-posting. You may kindly cross-post your code at the coding horror forum too.It is a crappy thing, but it's life -^ Carlo Pallini
Welcome pal. BTW That's wonderful. :-D
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong. -- Iain Clarke
[My articles] -
Welcome pal. BTW That's wonderful. :-D
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong. -- Iain Clarke
[My articles]Ah, thanks. :-O
It is a crappy thing, but it's life -^ Carlo Pallini