sön 2006-07-23 klockan 00:10 +0100 skrev Nick Kew: > But if you look at the full traceback and crossreference it to the > source, I think that looks improbable. Do you have sufficient gcc/gdb > expertise to shed real light on this?
Not really, only experience.. From what I have seen the causes to significantly garbled/nonsense arguments in stack traces is 7 of 10 -O2 somehow messing with the arguments or otherwise making gdb confused 2 of 10 smashed stacks in the called function 1 of 10 bugs in the calling function or earlier actually passing non-sense data to the function. The first and last can be identified by going up to the calling function and inspecting what the arguments should have been. The middle by hexdumping the stack contents, and looking at matching usage of nearby local arrays. Regards Henrik
signature.asc
Description: Detta är en digitalt signerad meddelandedel
