SIGSEGV in syslog(3)

[Adam H . Pendleton]

I am encountering a puzzling problem regarding a SIGSEGV when calling 
syslog(3).  I have tried using valgrind to see if I can find the source 
of the problem, but it does not occur when using valgrind.  The 
backtrace of the SIGSEGV is as follows:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 8192 (LWP 1895)]
0x42073b52 in _int_malloc () from /lib/i686/libc.so.6
(gdb) bt
#0  0x42073b52 in _int_malloc () from /lib/i686/libc.so.6
#1  0x42073155 in malloc () from /lib/i686/libc.so.6
#2  0x42069b26 in open_memstream () from /lib/i686/libc.so.6
#3  0x420d6219 in vsyslog () from /lib/i686/libc.so.6
#4  0x420d617f in syslog () from /lib/i686/libc.so.6
#5  0x08048e88 in process_requests () at program.c:104
#6  0x080494da in main (argc=2, argv=0xbffffb64) at program.c:327
#7  0x420158d4 in __libc_start_main () from /lib/i686/libc.so.6

From the limited search results that I have been able to turn up, this 
is apparantly caused by heap corruption occuring before the syslog() 
call, but for the life of me I can't figure out what could be causing 
any kind of head corruption, except...

There is a call to msgrcv() using a buffer which is malloc()'d before 
the syslog call.  Could this be the cause?  Am I missing something 
obvious.

I could not find a way to subscribe to this list, so please CC me when 
replying.  Any help would be much appreciated, as I have been pulling 
my hair out trying to figure this one out.

ahp

PGP.sig
Description: PGP signature