![]() ![]() You start looking near that code that you know ran, and you stop looking when you reach the code you know didn't run. You will have to use the debugger to narrow down the cause of your problem further, but the above possiblities should help you solve the riddle. These are sometimes known as "call back" functions. Since you mention that you are calling a third-party library, I will point out that it may be a situation of the library expecting you to provide a non- NULL function pointer as input to some API. This type of error, stack overflow, is the eponym of our forum. When the function later executes its ret instruction, the value 0x00000000 ( NULL) is loaded from the overwritten memory spot. The zeros have been written beyond the end of the stack buffer, over the preserved return address.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2023
Categories |