This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug libc/3824] Malloc reentrant occurs and corrupt memory even if _REENTRANT or/and THREAD_SAFE is set


------- Additional Comments From sanjeewaherath at yahoo dot com  2007-02-13 06:01 -------
Subject: Re:  Malloc reentrant occurs and corrupt memory even if _REENTRANT or/and THREAD_SAFE is set


Attempts to recreate the issue out side of purify was
a failure and I will provide the status after follow
up with purify,
Thanks
Sanjeewa

--- jakub at redhat dot com
<sourceware-bugzilla@sourceware.org> wrote:

> 
> ------- Additional Comments From jakub at redhat dot
> com  2007-02-12 12:41 -------
> Can you reproduce outside of purify?  Purify
> provides its own malloc, so if
> there is a malloc bug, it would be in purify, not in
> glibc malloc which isn't
> used at all.
> 
> -- 
>            What    |Removed                    
> |Added
>
----------------------------------------------------------------------------
>              Status|NEW                        
> |WAITING
> 
> 
> http://sourceware.org/bugzilla/show_bug.cgi?id=3824
> 
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
> You are on the CC list for the bug, or are watching
> someone who is.
> 



 
____________________________________________________________________________________
Do you Yahoo!?
Everyone is raving about the all-new Yahoo! Mail beta.
http://new.mail.yahoo.com


-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=3824

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]