Well, after checking and rechecking my libs, they are all built correctly as far as I can tell. I'm lost now. What's wierd is "stunnel" will error, but "stunnel --help" still runs and displays the usage and then exits. If I have a bogus config, it reads it, then errros. Can anyone who knows the code take a look this bottom of an strace and maybe point me to where the code is breaking, so I can try to find which library I have is broke?

_sysctl({{CTL_KERN, KERN_VERSION, 0, 20d91, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0}, 2, 0xbf964acc, 31, (nil), 0}) = 0
open("/etc/stunnel/stunnel.conf", O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40016000
read(3, "", 4096)                       = 0
close(3)                                = 0
munmap(0x40016000, 4096)                = 0
socket(PF_FILE, SOCK_DGRAM, 0)          = 3
fcntl64(3, F_SETFD, FD_CLOEXEC)         = 0
connect(3, {sa_family=AF_FILE, path="/dev/log"}, 16) = 0
mmap2(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40016000
time([1135895751])                      = 1135895751
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x4027e000
open("/usr/local/i386-tools/etc/localtime", O_RDONLY) = 4
fstat64(4, {st_mode=S_IFREG|0644, st_size=101, ...}) = 0
fstat64(4, {st_mode=S_IFREG|0644, st_size=101, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x4027f000
read(4, "TZif\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0\1\0"..., 4096) = 101
close(4)                                = 0
munmap(0x4027f000, 4096)                = 0
stat64("/usr/local/i386-tools/etc/localtime", {st_mode=S_IFREG|0644, st_size=101, ...}) = 0
stat64("/usr/local/i386-tools/etc/localtime", {st_mode=S_IFREG|0644, st_size=101, ...}) = 0
stat64("/usr/local/i386-tools/etc/localtime", {st_mode=S_IFREG|0644, st_size=101, ...}) = 0
writev(2, [{"Inconsistency detected by ld.so:"..., 33}, {"dl-minimal.c", 12}, {": ", 2}, {"134", 3}, {": ", 2}, {"realloc", 7}, {": ", 2}, {"Assertion `", 11}, {"ptr == alloc_last_block", 23}, {"\' failed!\n", 10}], 10Inconsistency detected by ld.so: dl-minimal.c: 134: realloc: Assertion `ptr == alloc_last_block' failed!
) = 105
exit_group(127)

----- Original Message -----

From: Michal Trojnara

Sent: Thursday, December 29, 2005 2:49 AM

Subject: RE: [stunnel-users] stunnel library inconsistencies

Here is what I've found googling on your problem:

http://www.mail-archive.com/openssl-dev@openssl.org/msg11649.html
I guess the problem is in your gcc or glibc.

BTW: stunnel 4.08 does not use realloc (but openssl does). 8-)

I've been using stunnel 4.08 on an embedded Linux platform for a while now, and am attempting to move to the 2.6 kernel from the 2.4.20, which has changed my building platform. I am cross-compiling with libs and tools targeted for the embedded system, which is an i486 type AMD Elan chip.

I have tried 4.08, 4.14 and 4.15b, all with the same result. Everything looks to compile properly, but when running stunnel I get the following:

Inconsistency detected by ld.so: dl-minimal.c: 134: realloc: Assertion `ptr == alloc_last_block' failed!

strace doesn't supply any helpful information. I have tried building with and without tcpwrappers, and have tried libssl 0.9.7g and 0.9.7i. Libssl v0.9.8a doesn't seem to play very nice.

Anyone able to look at my config.log? It's 140k uncompressed, but will zip it up if needed.