EHLO Andreas!
> > -incorrect malloc/realloc/free operations
> This includes:
> - Writing before or behind a malloced structure
> - accessing a malloced area after free has been called
Yes. The problem was in freeing, so i suppose it could be sth from this
area. but, I'll give you my wrapper's report:
[pborys@p-soft pinfo-0.4.6]$ ./pinfo bison 2>bison.log
[pborys@p-soft pinfo-0.4.6]$ tail bison.log
reallocating 134738928 to 134738928, with size 40
reallocating 134739000 to 134739000, with size 40
reallocating 134695024 to 134695024, with size 40
reallocating 134695096 to 134695096, with size 40
Allocated 134736768
Allocated 134739056
freeing 134721248
freeing 134734608
reallocating 134738928 to catched signal 11
pinfo: crash with: No such file or directory
[pborys@p-soft pinfo-0.4.6]$
(now a trace of use of the suspected memory block)
[pborys@p-soft pinfo-0.4.6]$ grep "134738928" bison.log
reallocating 134695024 to 134738928, with size 64
reallocating 134738928 to 134738928, with size 60
reallocating 134738928 to 134738928, with size 56
reallocating 134738928 to 134738928, with size 60
reallocating 134738928 to 134738928, with size 56
reallocating 134738928 to 134738928, with size 52
reallocating 134738928 to 134738928, with size 56
reallocating 134738928 to 134738928, with size 52
reallocating 134738928 to 134738928, with size 48
reallocating 134738928 to 134738928, with size 52
reallocating 134738928 to 134738928, with size 48
reallocating 134738928 to 134738928, with size 44
reallocating 134738928 to 134738928, with size 48
reallocating 134738928 to 134738928, with size 44
reallocating 134738928 to 134738928, with size 40
reallocating 134738928 to 134738928, with size 44
reallocating 134738928 to 134738928, with size 40
reallocating 134738928 to catched signal 11
[pborys@p-soft pinfo-0.4.6]$
> Looks really like a malloc problem. Run your application with
> MALLOC_CHECK_=1 or 2 in the environment to call some malloc self
> checks (this works with glibc2 and AFAIK also with later libc5
> versions).
With libc it didn't work, but I run it on a machine running glibc2, and
nothing was detected. :(
> > So? I'm really confused, I think I'll become grey because of this
> > And on my side, I'll take a closer look at the free() sources...
> Better check your code first, the malloc source should be ok.
I meant to find other possible points, which could cause a crash :)
> P.S. From the glibc2 manual:
[...]
Where do you have it from? Looks a bit better than the libc.info...
--
____\___\___
(_(\|,|_|,|_ Gassho! [http://dione.ids.pl/~pborys][mr MUA home]
| | |. [teksty o zen,programowaniu,moje sf,xfaq_pl, inne]
