From: Hagen Paul Pfeifer <hpplinuxml@0xdef.net>
To: linux-kernel@vger.kernel.org
Subject: Re: *** glibc detected *** nmap: malloc(): memory corruption: 0x08718a50 ***
Date: Tue, 1 Nov 2005 17:48:14 +0100 [thread overview]
Message-ID: <20051101164814.GA2671@0xdef.net> (raw)
In-Reply-To: <021a01c5df04$43d457e0$0400a8c0@dcccs>
* JaniD++ | 2005-11-01 17:49:43 [+0100]:
>I get this, on my dual-xeon ECC-reg memory system.
>What is this? :-)
Ask Fyodor! This is a glibc issue, who detects a memory corruption.
There _is_ a bug in nmap!
>kernel: 2.6.13
>(everything looks like normal)
No kernel issue! ;-)
>Janos
HGN
next prev parent reply other threads:[~2005-11-01 16:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-01 16:49 *** glibc detected *** nmap: malloc(): memory corruption: 0x08718a50 *** JaniD++
2005-11-01 16:48 ` Hagen Paul Pfeifer [this message]
2005-11-01 17:00 ` JaniD++
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051101164814.GA2671@0xdef.net \
--to=hpplinuxml@0xdef.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox