Mail Archives: djgpp-workers/2004/11/22/04:16:29
On Sun, 21 Nov 2004 fdonahoe AT wilkes DOT edu wrote:
> Call frame traceback EIPs:
> 0x00016416 free+69, file malloc.c
> 0x00017c6b popen+248, file popen.c
> 0x00006f72 .debug_info+982, file c:/djg/gnu/sed-4.1-2/ \
> sed/execute.c, line 1399
> 0x00002179 .comment+9
> 0x000157ad __crt1_startup+657, file crt1.c
>
> These programs are part of the libc.a source.
> The sizes and modification dates of these files are:
>
> -----m root 10928 Jun 13 2002 src/libc/ansi/stdlib/malloc.c
> -----m root 6071 Jun 1 23:08 src/libc/posix/stdio/popen.c
> -----m root 6570 Aug 19 23:08 src/libc/crt0/crt1.c
Could you compile malloc.c and popen.c with -g and reproduce the crash?
That would show the line numbers inside free and popen, which would be
helpful.
> Call frame traceback EIPs:
> 0x00016446 free+182, file ct_upper.c
> 0x00017e6b fread+75, file fread.c
> 0x00006fa2 .debug_info+1030, file c:/djg/gnu/sed-4.1-2/ \
> sed/execute.c, line 492
> 0x00002179 .comment+9
> 0x000157dd fprintf+45, file fprintf.c
>
> These programs are part of the libc.a source.
> The sizes and modification dates of these files are:
>
> -----m root 1761 Mar 10 2001 src/libc/ansi/ctype/ct_upper.c
> -----m root 2144 Oct 17 2002 src/libc/ansi/stdio/fread.c
> -----m root 693 Jun 8 2002 src/libc/ansi/stdio/fprintf.c
There seems to be something wrong with the output from symify (for one
thing, ct_upper.c has no function called free). Are you sure it was the
exact same executable that crashed and that you gave to symify as
argument?
--
Esa Peuha
student of mathematics at the University of Helsinki
http://www.helsinki.fi/~peuha/
- Raw text -