From: Daniel Jacobowitz <drow@false.org>
To: rtainewbie <rtainewbie@libero.it>
Cc: gdb <gdb@sources.redhat.com>
Subject: Re: gdb + mmap + /dev/mem
Date: Fri, 01 Apr 2005 17:21:00 -0000 [thread overview]
Message-ID: <20050401172051.GB19058@nevyn.them.org> (raw)
In-Reply-To: <IEA10O$5C11B39B82AF59A7BD34617F4F6C3DE1@libero.it>
On Fri, Apr 01, 2005 at 06:41:12PM +0200, rtainewbie wrote:
> I am trying to debug a simple application running on GNU-Linux kernel 2.6.8.1
> (see attachment).
>
> This application works in a memory region not visible for linux (parameter
> mem=XXX at boot time).
>
> I map this region using mmap on /dev/mem device as root user.
>
> When I debug it, accessing pointer to this region, the system freezes. So reboot
> is necessary and no debug is possible.
>
> The application work correcty but the only solution for debug it is running a
> concurrent application that writes the content of this memory region using printf.
>
> Does anybody know an easier and more confortable solution.
This is presumably a Linux kernel bug; you may want to talk to the
Linux kernel developers about it.
--
Daniel Jacobowitz
CodeSourcery, LLC
prev parent reply other threads:[~2005-04-01 17:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-01 16:41 rtainewbie
2005-04-01 17:21 ` 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=20050401172051.GB19058@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=rtainewbie@libero.it \
/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