ftp bug report

Wed Feb 18 14:45:00 GMT 2004

On 2004年2月18日, Thomas Mellman wrote:
> Re: ftp crash
> I tried to debug it with gdb but for some reason that I don't
> understand, it hangs when run.
>> Nevertheless, using gdb to get the symbols (which appear to
> be correct) and the ftp.exe.stackdump, I believe that I have
> localized the problem to the call to dataconn() in recvrequest().
> [snip]
> The funny thing is that the datacon() routine is in ftp.c, at
>> Local exec file:
> `/opt/pub/inetutils-1.3.2-25/ftp/ftp.exe', file type pei-i386.
> Entry point: 0x401000
> 0x00401000 - 0x0040cb04 is .text
> 0x0040d000 - 0x0040e280 is .data
> 0x0040f000 - 0x00411310 is .bss
> 0x00412000 - 0x00412ba4 is .idata
>> But the "entry point" for dataconn is somewhere completely different:
>> Exception: STATUS_ACCESS_VIOLATION at eip=610AB030
> eax=611489F4 ebx=00000038 ecx=7070736D edx=611489F4 esi=0A045018 edi=000001B0
> ebp=0022E9E8 esp=0022E9C8 program=D:\Programme\pub\inetutils-1.3.2-25\ftp\ftp.exe
> cs=001B ds=0023 es=0023 fs=0038 gs=0000 ss=0023
> Stack trace:
> Frame Function Args
> [snip]
> 0022EDB8 61086211 (00401083, 00405EDB, 0A044B70, 00000001)
>> ^ - dataconn?
> recvrequest - v
>> 0022EE88 00402E15 (00405EDB, 0A045258, 0A044B70, 00405E3C)
> [snip]
> End of stack trace (more stack frames may be present)
>> Or is these frames starting at 0x22edb8 (0x61086211) some kind
> of an interrupt?
>> Oh, perhaps the dataconn stack frame got lost somehow. Anyway,
> [strace output snipped]

0x61000000 is the base address for cygwin1.dll, IIRC.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
 |\ _,,,---,,_		pechtcha@cs.nyu.edu
ZZZzz /,`.-'`' -. ;-;;,_		igor@watson.ibm.com
 |,4- ) )-,_. ,\ ( `'-'		Igor Pechtchanski, Ph.D.
 '---''(_/--' `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster." -- Patrick Naughton
--
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/