kiorky wrote:
>
> kiorky a écrit :
>> (gdb)
>> 0x610bc6e2 in __small_vsprintf () from /usr/bin/cygwin1.dll
>> (gdb)
>> 0x610bc6e6 in __small_vsprintf () from /usr/bin/cygwin1.dll
>> (gdb)
>> 0x610bc6e9 in __small_vsprintf () from /usr/bin/cygwin1.dll
>> (gdb)
>> 0x61140ff0 in setlaster...@4 () from /usr/bin/cygwin1.dll
>> (gdb)
>> 0x7c94a156 in ntdll!RtlSetOwnerSecurityDescriptor () from
>> /cygdrive/c/WINDOWS/system32/ntdll.dll
>> (gdb)
>> 0x7c94a158 in ntdll!RtlSetOwnerSecurityDescriptor () from
>> /cygdrive/c/WINDOWS/system32/ntdll.dll
>> (gdb)
>> 0x7c94a159 in ntdll!RtlSetOwnerSecurityDescriptor () from
>> /cygdrive/c/WINDOWS/system32/ntdll.dll
>> (gdb)
>> 0x7c94a15b in ntdll!RtlSetOwnerSecurityDescriptor () from
>> /cygdrive/c/WINDOWS/system32/ntdll.dll
>> (gdb)
>> 0x7c94a161 in ntdll!RtlSetOwnerSecurityDescriptor () from
>> /cygdrive/c/WINDOWS/system32/ntdll.dll
>> (gdb)
>> 0x7c94a164 in ntdll!RtlSetOwnerSecurityDescriptor () from
>> /cygdrive/c/WINDOWS/system32/ntdll.dll
>> (gdb)
>> 0x7c94a167 in ntdll!RtlSetOwnerSecurityDescriptor () from
>> /cygdrive/c/WINDOWS/system32/ntdll.dll
>> (gdb)
>> Cannot access memory at address 0x8003
>> (gdb)
>> 0x610bc6ee in __small_vsprintf () from /usr/bin/cygwin1.dll
I think that "cannot access" message is just an artifact of something going
on in the internals of the win32 SetLastError function, and not a real problem
(also the symbols aren't accurate, it's not really in that rtl function).
Looking at the code around the addresses you indicate:
> 610bc6e2: 8b 54 24 2c mov 0x2c(%esp),%edx
> 610bc6e6: 89 14 24 mov %edx,(%esp)
> 610bc6e9: e8 02 49 08 00 call 61140ff0 <_setlaster...@4>
> 610bc6ee: 83 ec 04 sub $0x4,%esp
> 610bc6f1: 2b b4 24 60 80 00 00 sub 0x8060(%esp),%esi
... it sure seems like it has called SetLastError and then managed to return
to the __small_vsprintf routine successfully. So that error message is
/probably/ just a red herring.
> Uhm, i don't know how to advance on this one.
Sorry about the delay, I was AFK for a while, then had to download the
latest dll version to take a look at what those addresses indicate, and my
usual mirrors have been running a bit slow.
> I tried to reinstall all cygwin applications.
> Then recompile my geos stuff, but no success.
> Is there anything else to try?
Yeh. Maybe there's a DLL base-address collision going on and something's
forcing libstdc++ out of the way at runtime. Run it up to the crash under the
debugger, then take a look at the output from "info files". The addresses
where the DLLs are loaded should match what the output of "objdump -p
<dllname> | grep ImageBase" shows.
> When will we have a libstdc++ rebase-safe out to try ? Can i have it (email,
> or
> such) to try it waiting for that release?
Sure, I'll send it off-list.
cheers,
DaveK
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
