From: sseeger@stellartec.com (Steven Seeger)
To: <linux-mips@linux-mips.org>
Subject: mmap broken on cvs update 2_4
Date: Wed, 16 Jul 2003 07:01:33 -0700 [thread overview]
Message-ID: <004c01c34ba2$c499ba20$4383a8c0@WSSTEVELAPTOP> (raw)
In-Reply-To: <20030716014340.GA12436@nevyn.them.org>
The signal defined 1 problem is really a Bus error. uClibc is broken for
signals and got them from the x86 asm/signal.h file to build its default
string messages.
I'm using mmap. It maps successfully and has the proper ranges in
/proc/pid/maps.
When I try to access the memory I get a bus error. This did not happen
before I did a cvs update. I had even rebuilt a kernel prior to the cvs
update that didn't do that.
If someone can tell me where to look I'd appreciate it.
Steve
WARNING: multiple messages have this Message-ID (diff)
From: sseeger@stellartec.com (Steven Seeger)
To: linux-mips@linux-mips.org
Subject: mmap broken on cvs update 2_4
Date: Wed, 16 Jul 2003 07:01:33 -0700 [thread overview]
Message-ID: <004c01c34ba2$c499ba20$4383a8c0@WSSTEVELAPTOP> (raw)
Message-ID: <20030716140133.MhOcZugxksJXXIT0143kpomqOUcK53YeP4UG5nEnGnU@z> (raw)
In-Reply-To: <20030716014340.GA12436@nevyn.them.org>
The signal defined 1 problem is really a Bus error. uClibc is broken for
signals and got them from the x86 asm/signal.h file to build its default
string messages.
I'm using mmap. It maps successfully and has the proper ranges in
/proc/pid/maps.
When I try to access the memory I get a bus error. This did not happen
before I did a cvs update. I had even rebuilt a kernel prior to the cvs
update that didn't do that.
If someone can tell me where to look I'd appreciate it.
Steve
next prev parent reply other threads:[~2003-07-16 14:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-16 0:24 Help wanted WRT multigot David Daney
2003-07-16 1:43 ` Daniel Jacobowitz
2003-07-16 14:01 ` Steven Seeger [this message]
2003-07-16 14:01 ` mmap broken on cvs update 2_4 Steven Seeger
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='004c01c34ba2$c499ba20$4383a8c0@WSSTEVELAPTOP' \
--to=sseeger@stellartec.com \
--cc=linux-mips@linux-mips.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 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.