From: Andi Kleen <ak@muc.de>
To: Mark Studebaker <mds@mds.gotdns.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ancient portmap segfault
Date: Sun, 13 Mar 2005 11:08:38 +0100 [thread overview]
Message-ID: <m1d5u3yi1l.fsf@muc.de> (raw)
In-Reply-To: <4233B520.7010307@mds.gotdns.com> (Mark Studebaker's message of "Sat, 12 Mar 2005 22:36:00 -0500")
Mark Studebaker <mds@mds.gotdns.com> writes:
> I upgraded from 2.6.5 to 2.6.11.2 and my ancient (libc4 a.out) /sbin/portmap from 1994 that's been running without complaint
> on kernels for 11 years now consistently segfaults.
>
> I upgraded to a version 4 RPM (circa 2002) and that fixed it.
>
> If some compatibility was broken on purpose, that's fine, although I couldn't find anything in the kernel docs.
> I know, I should upgrade everything, but that can break a lot of things too...
> Thought I'd mention it though in case it's a bug or somebody else has the same problem.
It's probably a bug, but your bug report doesn't have enough details
to track it down. Do you have a a.out strace and could send an strace log
with the segfault and the last tens of system calls before it?
-Andi
next prev parent reply other threads:[~2005-03-13 10:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-13 3:36 ancient portmap segfault Mark Studebaker
2005-03-13 10:08 ` Andi Kleen [this message]
2005-03-15 3:07 ` Mark Studebaker
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=m1d5u3yi1l.fsf@muc.de \
--to=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mds@mds.gotdns.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.