Hrm, the upgrade from glibc-2.3.2 -> glibc-2.3.3 probably caused this.
Recompiled socks5v11 under glibc-2.3.3, now I get core dumps.
ls
---- Resolving host address...
Segmentation fault
Maybe it is no longer compatible.
#0 0x402db350 in _int_free () from /lib/libc.so.6
(gdb) bt
#0 0x402db350 in _int_free () from /lib/libc.so.6
#1 0x402d9fbf in free () from /lib/libc.so.6
#2 0x080ee7ec in lsConnectionDel ()
#3 0x080e48a1 in SOCKSclose ()
#4 0x080acb78 in Ftp::Connection::~Connection ()
#5 0x080ae458 in Ftp::ControlClose ()
#6 0x080b0d3f in Ftp::Disconnect ()
#7 0x080b05b0 in Ftp::SetError ()
#8 0x080b3168 in Ftp::ReceiveResp ()
#9 0x080b37e9 in Ftp::Do ()
#10 0x080898a2 in SMTask::Schedule ()
#11 0x0806c651 in WaitDone ()
#12 0x0806cd65 in main ()
(gdb) q
On Thu, 21 Oct 2004, Alexander V. Lukyanov wrote:
On Thu, Oct 21, 2004 at 04:20:46AM -0400, Justin Piszcz wrote:
/vapp/lib/libsocks5.a(addr.o)(.text+0xf5): In function `lsName2Port':
: undefined reference to `__ctype_b'
I think it is a problem within the socks5 library. It requires __ctype_b
symbol which should be supposedly provided by libc.
--
Alexander.
