Hello all,
I'm looking into a possible use of perdition here, but I'm seeing a
problem when I transmit certain characters, like CTRL-C, to perdition
configured for IMAP4.
It looks like it crashes for both the 1.19 RC2 and 1.18 versions, and it
appears the crash is actually inside libvanessa_logger.so.
For perdition-1.19rc2-1.1 and libvanessa_logger0-0.0.9-3.1:
*** glibc detected *** perdition: connect (
sanitized:36810->sanitized:5143): realloc(): invalid next size:
0x00000000081c76a0 ***
======= Backtrace: =========
/lib64/libc.so.6[0x3a406746b4]
/lib64/libc.so.6(realloc+0x102)[0x3a406751a2]
/usr/lib64/libvanessa_logger.so.0(vanessa_logger_str_dump+0xd2)[0x2b20cec8a742]
perdition: connect (
sanitized:36810->sanitized:5143)(token_read+0x23b)[0x40e71b]
perdition: connect (
sanitized:36810->sanitized:5143)(read_line+0x9a)[0x417e2a]
perdition: connect (
sanitized:36810->sanitized:5143)(imap4_in_get_auth+0x5a)[0x408d9a]
perdition: connect ( sanitized:36810->sanitized:5143)(main+0x855)[0x413e15]
/lib64/libc.so.6(__libc_start_main+0xf4)[0x3a4061d994]
perdition: connect ( sanitized:36810->sanitized:5143)[0x406509]
For version perdition-1.18-1.7 and libvanessa_logger0-0.0.8-18.2:
*** glibc detected *** perdition: connect: realloc(): invalid next size:
0x000000000100b330 ***
======= Backtrace: =========
/lib64/libc.so.6[0x3a406746b4]
/lib64/libc.so.6(realloc+0x102)[0x3a406751a2]
/usr/lib64/libvanessa_logger.so.0(vanessa_logger_str_dump+0xd2)[0x2b8240f6b742]
perdition: connect(token_read+0x23b)[0x4139fb]
perdition: connect(read_line+0x9a)[0x4130ba]
perdition: connect(imap4_in_get_pw+0x5a)[0x4074fa]
perdition: connect(main+0xb96)[0x40f866]
/lib64/libc.so.6(__libc_start_main+0xf4)[0x3a4061d994]
perdition: connect[0x405b19]
Has anyone seen this particular problem? Thanks!
--
Martin B. Smith
smithmb(a)ufl.edu - (352) 273-1374
CNS/Open Systems Group
University of Florida
Attachments:
- smime.p7s
(application/pkcs7-signature — 5.4 KB)