This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
Malloc problem
- From: "pstucklep" <pstucklep at CHARTER dot NET>
- To: <libc-alpha at sources dot redhat dot com>
- Date: Wed, 24 Mar 2004 21:47:18 -0600
- Subject: Malloc problem
- References: <20040325021216.GA10067@redhat.com>
Kind persons:
I recently upgraded from gcc.2.95.x to gcc-3.3.3 and its associated glibc.
My program still compiles but at runtime I now get a segmentation violation
from a malloc call. Did some major change go into malloc that is now more
strict than previous versions? Does anyone know what might be causing this
previously-running program to fail?
Thanks for any input.
Program received signal SIGSEGV, Segmentation fault.
0x00c7ab42 in _int_malloc () from /lib/tls/libc.so.6
(gdb) bt
#0 0x00c7ab42 in _int_malloc () from /lib/tls/libc.so.6
#1 0x00c7a5ae in calloc () from /lib/tls/libc.so.6
#2 0x0809c2de in alloc_perm (sMem=288) at db.c:3307
#3 0x0809a35d in create_mobile (pMobIndex=0xbee5b748) at db.c:2330
#4 0x08099c57 in reset_room (pRoom=0xbee5c1f0) at db.c:2104
#5 0x0809a311 in reset_area (pArea=0xbee5b394) at db.c:2313
#6 0x08099930 in area_update () at db.c:2001
#7 0x0810b163 in update_handler () at update.c:1887
#8 0x0808d02b in game_loop_unix (control=6) at comm.c:683
#9 0x0808c7f0 in main (argc=2, argv=0xbfebc614) at comm.c:393
Paul