debugging the break point? :) :)
-
is there any way i can trace the function where the breakpoint function was reached. I've tried the "crash finder" application but that couldnt trace the function either. I've put exception handlers all over but the application crashes at some point. The application always crashes at the same address and i cant really trace the condition where this is happening. I am writing all my the function names in a file to trace the condition but the application breaks off at a different point with the same address location. Any ideas people?
-
is there any way i can trace the function where the breakpoint function was reached. I've tried the "crash finder" application but that couldnt trace the function either. I've put exception handlers all over but the application crashes at some point. The application always crashes at the same address and i cant really trace the condition where this is happening. I am writing all my the function names in a file to trace the condition but the application breaks off at a different point with the same address location. Any ideas people?
-
is there any way i can trace the function where the breakpoint function was reached. I've tried the "crash finder" application but that couldnt trace the function either. I've put exception handlers all over but the application crashes at some point. The application always crashes at the same address and i cant really trace the condition where this is happening. I am writing all my the function names in a file to trace the condition but the application breaks off at a different point with the same address location. Any ideas people?
-
is there any way i can trace the function where the breakpoint function was reached. I've tried the "crash finder" application but that couldnt trace the function either. I've put exception handlers all over but the application crashes at some point. The application always crashes at the same address and i cant really trace the condition where this is happening. I am writing all my the function names in a file to trace the condition but the application breaks off at a different point with the same address location. Any ideas people?
Anonymous wrote: The application always crashes at the same address and i cant really trace the condition where this is happening. Have a look at the project's .map file (you might have to add /map to the linker settings). For example, if you know the program is crashing at address 0x17d28a03, you would look in the .map file for the closest address that is less than this value.
"Opinions are neither right nor wrong. I cannot change your opinion of me. I can, however, change what influences your opinion." - David Crow