On Sat, 13 Mar 2010 09:47:09 +0100, Danny Backx <danny.ba...@dqsdqsdqdd.be> wrote: > On Wed, 2010-03-10 at 21:15 +0100, Danny Backx wrote: >> Meaning, I think, that it does indeed crash in that statement. The >> double "ldr r3, [r3]" seems odd. Even more odd is that the code in >> a/t.dll.objdump is different : it looks exactly the same except only one >> of these "ldr r3, [r3]" instructions. >> >> Trying to figure out which one is correct, and how to debug at the >> assembler level :-( > > It would appear that in this sample program, the crash is legitimate > because - yet again - an invalid pointer is read. The value of 0x16342b8 > which is in r3 is not a valid pointer. > > In the second debugging session below I dug deeper and fixed the value > of r3 which executing, which made the program work well. > > I'll try to find the cause of this now... >
Ok when reading some post on mingw mailing list,I could read the following lines : "With those conditions, the lack of an -enable-auto-import switch does not cause the 0xc0000005 error that ld warns about here: "warning: auto-importing has been activated without --enable-auto-import specified on the command line. This should work unless it involves constant data structures referencing" If you want to make --enable-auto-import the default, which makes sense with Kai's pseudo-reloc fixes, the place to do it is in src/ld/pe.em (not in gcc specs)." It looks like some of the issues you have reported about external symbols. Maybe it can help ? ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Cegcc-devel mailing list Cegcc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cegcc-devel
