This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: debugging cygwin
- From: Ken Senior <senior at juno dot nrl dot navy dot mil>
- To: cygwin at cygwin dot com
- Date: Tue, 10 Jan 2006 15:28:59 -0500
- Subject: Re: debugging cygwin
- Reply-to: cygwin at cygwin dot com
Having regrouped with a new sense of hope I have tried once again....
1. I changed the admin account on my Windows XP machine to admin,
instead of senior. In the following test, I utilized only the local
admin account (no domain accounts whatsoever) on [Windows Box]
2. On [Windows Box] I reinstalled cygwin using the admin account
3. On [Windows Box] I compiled and installed (with debugging) the
rsync.exe program
4. On [Windows Box] I successfully installed (following the exact
directions on the FAQ) the snapshot dated 1/10, including the .dbg file
5. I rebooted [Windows Box] to ensure correct snapshot dll was loaded
6. On [Linux] I inititiated the rysnc command:
rsync -avvvvvvz --rsh="ssh -l admin" admin@[Windows Box]:/path/to/stuff/
./test
7. On [Windows Box], I used ps to find the PID of the rsync process
8. On [Windows Box] I launched 'gdb rsync PID'
9. In gdb I issued all of the following:
(gdb) add-symbol-file /usr/bin/cygwin1.dbg
add symbol table from file "/usr/bin/cygwin1.dbg" at
(y or n) y
Reading symbols from /usr/bin/cygwin1.dbg...warning: no loadable
sections found
in added symbol-file /usr/bin/cygwin1.dbg
done.
(gdb) thread info
No symbol "info" in current context.
(gdb) info thread
* 4 thread 4044.0x520 0x7c901231 in ntdll!DbgUiConnectToDbg ()
from /cygdrive/c/WINDOWS/system32/ntdll.dll
3 thread 4044.0x240 0x7c90eb94 in ntdll!LdrAccessResource ()
from /cygdrive/c/WINDOWS/system32/ntdll.dll
2 thread 4044.0xfc4 0x7c90eb94 in ntdll!LdrAccessResource ()
from /cygdrive/c/WINDOWS/system32/ntdll.dll
1 thread 4044.0xfb8 0x7c90eb94 in ntdll!LdrAccessResource ()
from /cygdrive/c/WINDOWS/system32/ntdll.dll
(gdb) thread 4
[Switching to thread 4 (thread 4044.0x520)]#0 0x7c901231 in
ntdll!DbgUiConnectT
oDbg () from /cygdrive/c/WINDOWS/system32/ntdll.dll
(gdb) bt
#0 0x7c901231 in ntdll!DbgUiConnectToDbg ()
from /cygdrive/c/WINDOWS/system32/ntdll.dll
#1 0x7c9507a8 in ntdll!KiIntSystemCall ()
from /cygdrive/c/WINDOWS/system32/ntdll.dll
#2 0x00000005 in ?? ()
#3 0x00000004 in ?? ()
#4 0x00000001 in ?? ()
#5 0x18e8ffd0 in ?? ()
#6 0x00017451 in ?? ()
#7 0xffffffff in ?? ()
#8 0x7c90ee18 in strchr () from /cygdrive/c/WINDOWS/system32/ntdll.dll
#9 0x7c9507c8 in ntdll!KiIntSystemCall ()
from /cygdrive/c/WINDOWS/system32/ntdll.dll
#10 0x00000000 in ?? () from
(gdb) thread 3
[Switching to thread 3 (thread 4044.0x240)]#0 0x7c90eb94 in
ntdll!LdrAccessReso
urce () from /cygdrive/c/WINDOWS/system32/ntdll.dll
(gdb) bt
#0 0x7c90eb94 in ntdll!LdrAccessResource ()
from /cygdrive/c/WINDOWS/system32/ntdll.dll
#1 0x7c90e9c0 in ntdll!ZwWaitForSingleObject ()
from /cygdrive/c/WINDOWS/system32/ntdll.dll
#2 0x7c8025db in WaitForSingleObjectEx ()
from /cygdrive/c/WINDOWS/system32/kernel32.dll
#3 0x00000748 in ?? ()
#4 0x00000000 in ?? () from
(gdb) thread 2
[Switching to thread 2 (thread 4044.0xfc4)]#0 0x7c90eb94 in
ntdll!LdrAccessReso
urce () from /cygdrive/c/WINDOWS/system32/ntdll.dll
(gdb) bt
#0 0x7c90eb94 in ntdll!LdrAccessResource ()
from /cygdrive/c/WINDOWS/system32/ntdll.dll
#1 0x7c90e288 in ntdll!ZwReadFile ()
from /cygdrive/c/WINDOWS/system32/ntdll.dll
#2 0x7c801875 in ReadFile () from /cygdrive/c/WINDOWS/system32/kernel32.dll
#3 0x0000075c in ?? ()
#4 0x00000000 in ?? () from
(gdb) thread 1
[Switching to thread 1 (thread 4044.0xfb8)]#0 0x7c90eb94 in
ntdll!LdrAccessReso
urce () from /cygdrive/c/WINDOWS/system32/ntdll.dll
(gdb) bt
#0 0x7c90eb94 in ntdll!LdrAccessResource ()
from /cygdrive/c/WINDOWS/system32/ntdll.dll
#1 0x7c90e9ff in ntdll!ZwWriteFile ()
from /cygdrive/c/WINDOWS/system32/ntdll.dll
#2 0x7c81100e in WriteFile () from
/cygdrive/c/WINDOWS/system32/kernel32.dll
#3 0x00000694 in ?? ()
#4 0x00000000 in ?? () from
(gdb)
However, it looks like after all this, I'm still not getting debugging
information for rsync. My understanding of gdb consists only from that
gleaned from this thread. Christopher Faylor alluded to some other
problems, but I'm not sure what he means or what is the next step.
Perhaps I must give up now. I would have thought this problem (rsync
hanging) to be more pervasive, particularly since the use of rsync to
back up systems (both Linux and Windows) seems to me a good one. I
appreciate everyone's patience as my hope is fading. -K
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/