public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libc/3462] New: Malloc memory corruption when malloc(...) called
@ 2006-11-06 20:15 jrweave at gmail dot com
2006-11-06 20:35 ` [Bug libc/3462] " drepper at redhat dot com
0 siblings, 1 reply; 2+ messages in thread
From: jrweave at gmail dot com @ 2006-11-06 20:15 UTC (permalink / raw)
To: glibc-bugs
I simple call to malloc results in the following error:
*** glibc detected *** malloc(): memory corruption: 0x00000000005b61c0 ***
I am requesting 5750*380*8 (17,480,000) bytes of data. I am running on an
Intel Woodcrest system (em64t architecture). Many calls to malloc ask for
similar sizes of memory before this call, but none of them fail. This call
consistently fails every time.
Due to the complexity and proprietary nature of the code, I cannot send a
sample. However, it occurs exactly as described above.
--
Summary: Malloc memory corruption when malloc(...) called
Product: glibc
Version: 2.3.4
Status: NEW
Severity: critical
Priority: P2
Component: libc
AssignedTo: drepper at redhat dot com
ReportedBy: jrweave at gmail dot com
CC: glibc-bugs at sources dot redhat dot com,jrweave at
gmail dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=3462
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
^ permalink raw reply [flat|nested] 2+ messages in thread
* [Bug libc/3462] Malloc memory corruption when malloc(...) called
2006-11-06 20:15 [Bug libc/3462] New: Malloc memory corruption when malloc(...) called jrweave at gmail dot com
@ 2006-11-06 20:35 ` drepper at redhat dot com
0 siblings, 0 replies; 2+ messages in thread
From: drepper at redhat dot com @ 2006-11-06 20:35 UTC (permalink / raw)
To: glibc-bugs
------- Additional Comments From drepper at redhat dot com 2006-11-06 20:35 -------
The message clearly says that glibc *detected* the problem. Not caused it.
Your program is corrupting memory somewhere somehow and glibc finally notices
it. Use valgrind or mudflap or similar tools to detect your mistake.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
http://sourceware.org/bugzilla/show_bug.cgi?id=3462
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2006-11-06 20:35 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-11-06 20:15 [Bug libc/3462] New: Malloc memory corruption when malloc(...) called jrweave at gmail dot com
2006-11-06 20:35 ` [Bug libc/3462] " drepper at redhat dot com
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).