Re: *** glibc detected *** malloc(): memory corruption: 0x09d9a8a8 ***

• To: For users of Fedora Core releases <fedora-list@xxxxxxxxxx>
• Subject: Re: *** glibc detected *** malloc(): memory corruption: 0x09d9a8a8 ***
• From: Ulrich Drepper <drepper@xxxxxxxxxx>
• Date: Sat, 12 Feb 2005 12:12:50 -0800
• In-reply-to: <[email protected]>
• List-archive: <https://www.redhat.com/archives/fedora-list>
• List-help: <mailto:[email protected]?subject=help>
• List-id: For users of Fedora Core releases <fedora-list.redhat.com>
• List-post: <mailto:[email protected]>
• List-subscribe: <http://www.redhat.com/mailman/listinfo/fedora-list>, <mailto:[email protected]?subject=subscribe>
• List-unsubscribe: <http://www.redhat.com/mailman/listinfo/fedora-list>, <mailto:[email protected]?subject=unsubscribe>
• Organization: Red Hat, Inc.
• References: <[email protected]>
• Reply-to: For users of Fedora Core releases <fedora-list@xxxxxxxxxx>
• User-agent: Mozilla Thunderbird (X11/20041216)

Clinton Parham wrote:

This means you come across a bug in xmodmap where it corrupts memory.
As the message says, glibc only detects these things, it doesn't cause
them.  File a bug for xmodmap and show the exact input file and command
line parameters.

--
â Ulrich Drepper â Red Hat, Inc. â 444 Castro St â Mountain View, CA â

• References:
  • *** glibc detected *** malloc(): memory corruption: 0x09d9a8a8 ***
    • From: Clinton Parham

• Prev by Date: Re: trying to change IO scheduler
• Next by Date: Re: LVM, resize /, & FC3 defaults
• Previous by thread: *** glibc detected *** malloc(): memory corruption: 0x09d9a8a8 ***
• Next by thread: Updating Fedora 3 non-internet
• Index(es):
  • Date
  • Thread