Trouble isolating x64 slowdown

David Morgan dmorgan@aechelon.com
Thu Jan 28 23:32:00 GMT 2010


On Wed, Jan 27, 2010 at 11:41:55PM -0600, David Morgan wrote:
> I think I'm getting the hang of it now.  All it takes is a little alcohol...

Wow - sorry if this came across as an insult.  I was debugging after a glass
of wine myself, and that was not my intention.

> + objcopy -j .stab -j .stabstr cygwin0.dll cygwin1.dbg
> + objcopy -g --add-gnu-debuglink=cygwin1.dbg cygwin0.dll
> + objcopy -R .gnu_debuglink_overlay --set-section-flag .gnu_debuglink=contents,r
> eadonly,debug,noload --change-section-address .idata=0x6115f000 --change-section
> -address .cygheap=0x6116f000 --change-section-address .gnu_debuglink=0x6117f000
> cygwin0.dll

I managed to build a working DLL by tweaking the above objcopy commands to 
conform the results to the stock DLL's headers.  I don't know why the perl
script is getting it wrong.

objcopy -j .stab -j .stabstr cygwin0.dll cygwin1.dbg
objcopy -g --add-gnu-debuglink=cygwin1.dbg cygwin0.dll
objcopy -R .gnu_debuglink_overlay --set-section-flag .gnu_debuglink=contents,readonly,debug,noload --change-section-address .gnu_debuglink=0x6115f000 cygwin0.dll

I'll post when I have some results regarding the x64 slowdown.

Regards,

David



More information about the Cygwin-developers mailing list