[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Malloc bug?
From: |
wmglo |
Subject: |
Re: Malloc bug? |
Date: |
7 Aug 2003 22:07:24 -0000 |
Hi,
> I'm using a 2.2.4 based (errata, -34 I believe) glibc that is distributed
> with Red Hat for x86. I've got a problem with a multithreaded application I
> have created; The program stops exectution without terminating. Running it
> through gdb reveals:
>
> #0 0x4008cbb5 in __sigsuspend (set=0x4d9fe948)
> at ../sysdeps/unix/sysv/linux/sigsuspend.c:45
> #1 0x400521d9 in __pthread_wait_for_restart_signal (self=0x4d9ffbe0)
> at pthread.c:969
> #2 0x40053a2c in __pthread_lock (lock=0x4001649c, self=0x4d9ffbe0)
> at spinlock.c:149
> #3 0x40050d46 in __pthread_mutex_lock (mutex=0x4001648c) at mutex.c:109
> #4 0x40177e50 in _dl_open (file=0x4d9fed5e "/lib/security/pam_unix.so",
> mode=-2147483646, caller=0x4019d8ef) at dl-open.c:401
What makes you think this has to do with malloc (subject)?
Can you post sample code exibiting the problem?
Regards,
Wolfram.
- Malloc bug?, Joshua_Giles, 2003/08/07
- Re: Malloc bug?,
wmglo <=