From: Pedro Alves <pedro@codesourcery.com>
To: gdb@sourceware.org
Cc: Niklas Quarfot Nielsen <nik@qni.dk>
Subject: Re: GDB remote debugging stub: Question about memory read
Date: Mon, 27 Sep 2010 09:16:00 -0000 [thread overview]
Message-ID: <201009271016.32726.pedro@codesourcery.com> (raw)
In-Reply-To: <1257E26A-12FB-432E-A18C-137440C02080@qni.dk>
On Monday 27 September 2010 09:54:04, Niklas Quarfot Nielsen wrote:
> GDB tries to read 0x40 bytes starting at address 0xffffffff6effffc0, which (I guess) is from the RSP.
> Packet: mffffffff6effffc0,40
>
> My question is:
> Why does GDB try to read 0x40 bytes, when there is only 0x20 bytes on the stack (RBP-RSP)?
>
> The architecture is an AMD64 and the version of GDB is 7.1(x86_64-gnu-linux).
>
> I appreciate any answer and/or clue to why GDB behaves like this.
> I have tried to look through the remote debugging source code of GDB, but this has not given me any answers.
> If needed, I can post debugging information from the target code in GDB.
>
0x40 bytes is GDB's stack cache line size (dcache.c).
Try "(gdb) set stack-cache off".
--
Pedro Alves
next prev parent reply other threads:[~2010-09-27 9:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-27 8:54 Niklas Quarfot Nielsen
2010-09-27 9:16 ` Pedro Alves [this message]
2010-09-27 9:20 ` Niklas Quarfot Nielsen
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=201009271016.32726.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb@sourceware.org \
--cc=nik@qni.dk \
/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