Mail Archives: cygwin/2001/10/09/13:32:13
Christopher Faylor wrote:
>
>
> I've duplicated the stack dump. It's coming from free and it is due
> to memory corruption. Something in perl is corrupting the heap.
>
> AFAICT, it isn't a Cygwin problem.
>
> I suspect that there might be some problem with a misconfigured perl,
> maybe? I know that perl can use its own version of malloc. I wonder
> if some memory that is allocated by perl's malloc has been passed to
> cygwin's malloc for freeing. If so, then *boom*.
That is a distinct possibility. I could see that Perl_safesysfree was
being called, but all of those things should have been created with
Perl_safemalloc. These are both wrappers around the system malloc()
and free() so it is an avenue of investigation at least. I'll look at
the wrapper code and see if there is anything that has changed recently.
But, would this mean that if miniperl is being run under gdb, there
would be no core dump? Because that is the behavior I am seeing
(once I downgraded to CygWin 1.3.2-2).
--
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4720 Boston Way
Lanham, MD 20706
301-459-3366 x.5010
fax 301-429-5747
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -