From: Daniel Jacobowitz <drow@false.org>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: segfaults due to mmap (umoven: Input/Output error)
Date: Fri, 29 Oct 1999 13:22:51 -0400 [thread overview]
Message-ID: <19991029132251.A1336@drow.res.cmu.edu> (raw)
In-Reply-To: <99102917335900.03412@localhost.localdomain>; from Wolfgang Haeuptli on Fri, Oct 29, 1999 at 05:28:13PM +0200
No, that's not an error in the program, it's an error in strace. The
latest version of strace corrects it. You need to get the Debian
package of it; I don't know where else it's available. The new home
for it isn't up yet.
Look for strace_*.orig.tar.gz in
ftp://ftp.debian.org/debian/dists/unstable/main/source/devel/
On Fri, Oct 29, 1999 at 05:28:13PM +0200, Wolfgang Haeuptli wrote:
>
> Hello everybody
>
> Several programs I compiled recently die with a segfault.
> strace shows:
> mmap (ptrace: umoven: Inout/Output Error...
>
> There are lots of remarks about mmap-problems, but I didn't find a clear
> solution. Is that a problem with glibc?
> I'm using kernel 2.2.9 with glibc-2.1.1-6c. Would a glibc-update fix the
> problem, or does somebody suggests something else?
>
> Thanks
>
> Wolfgang Haeuptli
>
>
Dan
/--------------------------------\ /--------------------------------\
| Daniel Jacobowitz |__| SCS Class of 2002 |
| Debian GNU/Linux Developer __ Carnegie Mellon University |
| dan@debian.org | | dmj+@andrew.cmu.edu |
\--------------------------------/ \--------------------------------/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~1999-10-29 17:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-29 15:28 segfaults due to mmap (umoven: Input/Output error) Wolfgang Haeuptli
1999-10-29 17:22 ` Daniel Jacobowitz [this message]
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=19991029132251.A1336@drow.res.cmu.edu \
--to=drow@false.org \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).