From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3993 invoked by alias); 1 Apr 2005 17:21:13 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 3841 invoked from network); 1 Apr 2005 17:20:52 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sourceware.org with SMTP; 1 Apr 2005 17:20:52 -0000 Received: from drow by nevyn.them.org with local (Exim 4.50 #1 (Debian)) id 1DHPpD-000500-HO; Fri, 01 Apr 2005 12:20:51 -0500 Date: Fri, 01 Apr 2005 17:21:00 -0000 From: Daniel Jacobowitz To: rtainewbie Cc: gdb Subject: Re: gdb + mmap + /dev/mem Message-ID: <20050401172051.GB19058@nevyn.them.org> Mail-Followup-To: rtainewbie , gdb References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6+20040907i X-SW-Source: 2005-04/txt/msg00007.txt.bz2 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