c/3766: malloc
hankh@dacom.net
hankh@dacom.net
Sun Jul 22 19:16:00 GMT 2001
>Number: 3766
>Category: c
>Synopsis: malloc
>Confidential: no
>Severity: critical
>Priority: high
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Sun Jul 22 19:16:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: dacom
>Release: unknown-1.0
>Organization:
>Environment:
gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-81)
>Description:
This phclitest is test on Solaris 5.7 with gcc version 2.95.3 20010315 (release)
But it generate core file in malloc().
I use calloc() instead of malloc. but it crashed.
gdb's message like this
Core was generated by `./phclitest freecas'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /lib/i686/libc.so.6...
done.
Loaded symbols for /lib/i686/libc.so.6
Reading symbols from /lib/ld-linux.so.2...done.
Loaded symbols for /lib/ld-linux.so.2
#0 0x400ae00a in chunk_free (ar_ptr=0x40156f00, p=0x4805c978) at malloc.c:3125
3125 malloc.c: No such file or directory.
in malloc.c
(gdb)
(gdb) bt
#0 0x400ae00a in chunk_free (ar_ptr=0x40156f00, p=0x4805c978) at malloc.c:3125
#1 0x400ad716 in chunk_alloc (ar_ptr=0x40156f00, nb=88) at malloc.c:2612
#2 0x400ad13a in __libc_malloc (bytes=77) at malloc.c:2714
#3 0x0804ff4c in MakePhCasfReq (pPhCtx=0xbfffd4c0) at phmsg_proc.c:550
#4 0x080501df in MakeSendMsg (pPhCtx=0xbfffd4c0) at phmsg_proc.c:609
#5 0x08049d17 in rPhFreeCasReq (pIp=0x80562fb "172.26.36.27", nPort=10240,
pMid=0x8056280 "tfinlinux", pOid=0x805628a "ntkys02200105041450292414",
pAddr=0xbfffd5c0 "addr1111", pItem=0xbfffd580 "iTem1111",
pszRespCd=0xbfffd8f0 "", pszErrMsg=0xbfffd7a0 "") at phcli.c:98
#6 0x0804909c in main (ac=2, av=0xbffffa0c) at phclitest.c:70
#7 0x4004a177 in __libc_start_main (main=0x8048d70 <main>, argc=2,
ubp_av=0xbffffa0c, init=0x80489a8 <_init>, fini=0x8056240 <_fini>,
rtld_fini=0x4000e184 <_dl_fini>, stack_end=0xbffff9fc)
at ../sysdeps/generic/libc-start.c:129
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the Gcc-bugs
mailing list