From: Marc TITINGER <Marc.TITINGER@st.com>
To: Kevin Pouget <kevin.pouget@gmail.com>,
"gdb@sources.redhat.com" <gdb@sources.redhat.com>
Cc: MikeW <mw_phil@yahoo.co.uk>
Subject: RE: Can gdb handle aliased memory regions ?
Date: Fri, 14 Oct 2011 07:54:00 -0000 [thread overview]
Message-ID: <5A300A8A9D10DF4EBD1BE0537D30AA9DB77C04FB98@SAFEX1MAIL4.st.com> (raw)
In-Reply-To: <CAPftXUKTyXBy3a0Sjyv5=5yZvsy=bPLs9YzdxAoeMbfMT-Jtmg@mail.gmail.com>
Hi Mike,
> -----Original Message-----
> From: Kevin Pouget [mailto:kevin.pouget@gmail.com]
> Sent: Thursday, October 13, 2011 6:16 PM
> To: gdb@sources.redhat.com
> Cc: MikeW; Marc TITINGER
> Subject: Re: Can gdb handle aliased memory regions ?
>
> On Wed, Oct 12, 2011 at 5:35 PM, MikeW <mw_phil@yahoo.co.uk> wrote:
> > Target platform: STLinux / ST Micro Connect
> >
> > On the target CPU, there is one region of physical memory that is
> accessible by
> > two different mapped memory address regions: one as cached memory and
> one as
> > uncached, eg.
> > 0x8000000 (virt cached) -> 0x40000000 (phys)
> > 0xDF00000 (virt uncached) -> 0x40000000 (phys)
Is it 0xDF00000 or 0xDF00_0000 like below in this text ? I'm asking because in the first case it looks like a VM (usermode) to Phy translation issue (I'm assuming it is a Linux kernel), while below, it looks like a kernel to physical memory mapping question ?
> >
> > During the kernel init, there is a code sequence which switches
> between cached
> > and uncached (to update cache registers etc) and expects the
> execution to
> > proceed from eg. 0x80001234 to 0xDF001236.
So IIUC, you are running kernel code and at that point you which to tell the debugger to use a different offset and resume. Maybe the kernel has a meminfo.bank dedicated to the uncached mapping that we could use.
> >
> > Stepping with gdb is fine until the switchover point is reached,
> > whereupon gdb thinks it's lost control ('step[i]', 'next' or 'finish'
> > do not return to the (gdb) prompt), but of course the ms bits of
> > the PC just refer to the other region.
> >
> > I note gbd has support for the older technique of overlays; is there
> any way to
> > tell gdb that the 0x8000... and 0xDF00... regions are actually the
> same physical
> > memory ?
AFAIK the linux-awareness target does not support this currently unfortunately, but it would be easy to add a command to switch the memory bank from the tty at that point.
May I ask you to send me the type of SoC, stlinux and gdb versions you are using ?
Many thanks,
Marc.
> >
> > Thanks.
>
> stlinux kernel debugger maintainer cc'd
next prev parent reply other threads:[~2011-10-14 7:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-12 15:40 MikeW
2011-10-13 16:16 ` Kevin Pouget
2011-10-14 7:54 ` Marc TITINGER [this message]
2011-10-14 13:21 ` MikeW
2011-10-19 20:21 ` Tom Tromey
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=5A300A8A9D10DF4EBD1BE0537D30AA9DB77C04FB98@SAFEX1MAIL4.st.com \
--to=marc.titinger@st.com \
--cc=gdb@sources.redhat.com \
--cc=kevin.pouget@gmail.com \
--cc=mw_phil@yahoo.co.uk \
/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