Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: <j_clifton@aerosimulation.com>
To: <gdb@sourceware.cygnus.com>
Subject: Re: examining mmap()'d memory regions on linux
Date: Mon, 05 Jun 2000 18:01:00 -0000	[thread overview]
Message-ID: <0006059602.AA960253227@mailserver.aerosimulation.com> (raw)

>Kevin Hilman wrote on 17 May 2000:
>> 
>> I have an app that reads/writes to an mmap()'d region.  The data
>> is being read and written fine because it's getting to it's final
>> location (in this case a hardware device).
>> 
>> However, if I try to examine (via 'x') these memory regions in gdb, I
>> always get zeros.
>> 
>> Does gdb support mmap()'d regions?
>
>Not a GDB problem.  GDB asks the kernel ``can I have memory at address X
>with process P''.  If the kernel doesn't return it there is little GDB
>can do :-)
>
>As a work around, you may want to add a small function to your program
>that dumps out the relevant data.  You can then call that from the gdb
>command line.
>
>   enjoy,
>       Andrew

Can you elaborate on what/how the kernel (ptrace) returns zero for mmapped
memory?
I read the ptrace.c code for i386 and didn't see the relationship between the
comments and mmap. I have the same problem with unable to examine a PCI
reflective memory. I also tried a program which just mallocs memory and I
couldn't see it's contents either.


             reply	other threads:[~2000-06-05 18:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-05 18:01 j_clifton [this message]
     [not found] <r23dngrjg9.fsf@bobdog.equator.com>
2000-05-17 14:55 ` Mark Kettenis
2000-05-17 16:34 ` Andrew Cagney

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=0006059602.AA960253227@mailserver.aerosimulation.com \
    --to=j_clifton@aerosimulation.com \
    --cc=gdb@sourceware.cygnus.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox