From: Luis Machado via Gdb <gdb@sourceware.org>
To: Phil Phil <heidegg@hotmail.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Stack segments for Aarch64
Date: Thu, 6 Jun 2024 10:41:48 +0100 [thread overview]
Message-ID: <d05e693f-cba0-40bc-b333-e896e85867b9@arm.com> (raw)
In-Reply-To: <PH7PR22MB4048B7E258D3D1FF7E6A4EEDAAFA2@PH7PR22MB4048.namprd22.prod.outlook.com>
Hi,
On 6/6/24 10:33, Phil Phil wrote:
> GDB 12.1 coredump post mortem coredump debugging on an x64 Linux desktop. I do not see a perms column in info proc mappings.
>
Ah, so it is corefile debugging. Checking on my end, I don't see the permissions column either. Now it escapes me if we have any
special reason for that or if it is just an oversight somewhere. As for the stack marker, I suppose we lose that reference
when the corefile is generated. That reference comes from /proc/<pid>/maps when we do "info proc mapping".
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> *From:* Luis Machado <luis.machado@arm.com>
> *Sent:* Thursday, June 6, 2024 9:23 AM
> *To:* Phil Phil <heidegg@hotmail.com>; gdb@sourceware.org <gdb@sourceware.org>
> *Subject:* Re: Stack segments for Aarch64
>
> Hi,
>
> On 6/6/24 10:17, Phil Phil via Gdb wrote:
>> Greetings,
>>
>> I'm trying get some memory info on an Aarch64 for a coredump. The aarch64 gdb produces this output for info proc mappings
>>
>> Start Addr End Addr Size Offset objfile
>> 0x557ead9000 0x5582dee000 0x4315000 0x0 /usr/bin/myproc
>> 0x5582dfe000 0x5582f0a000 0x10c000 0x4315000 /usr/bin/myproc
>> 0x5582f0a000 0x5582f24000 0x1a000 0x4421000 /usr/bin/myproc
>>
>> I'm missing at least two things here compared to the x64 output:
>>
>>
>> *
>> No read/write permissions
>> *
>> Stack segments are not shown.
>>
>> Any ideas on how to make these two things visible on Aarch64?
>>
>> Regards
>
> What aarch64 debugging setup do you have? Versions etc? Remote?
>
> For me, running native gdb on aarch64:
>
> process 1681741
> Mapped address spaces:
>
> Start Addr End Addr Size Offset Perms objfile
> 0xaaaaaaaa0000 0xaaaaac3c6000 0x1926000 0x0 r-xp /home/ubuntu/work/build/binutils-gdb-master/gdb/gdb
> 0xaaaaac3d5000 0xaaaaacd2a000 0x955000 0x1925000 r--p /home/ubuntu/work/build/binutils-gdb-master/gdb/gdb
> 0xaaaaacfc6000 0xaaaaad069000 0xa3000 0x0 rw-p [heap]
> ...
> 0xfffffffdf000 0x1000000000000 0x21000 0x0 rw-p [stack]
next prev parent reply other threads:[~2024-06-06 9:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 9:17 Phil Phil via Gdb
2024-06-06 9:23 ` Luis Machado via Gdb
2024-06-06 9:33 ` Phil Phil via Gdb
2024-06-06 9:41 ` Luis Machado via Gdb [this message]
2024-06-06 9:57 ` Phil Phil via Gdb
2024-06-06 10:15 ` Luis Machado via Gdb
2024-06-06 10:27 ` Phil Phil via Gdb
2024-06-06 10:29 ` Luis Machado via Gdb
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=d05e693f-cba0-40bc-b333-e896e85867b9@arm.com \
--to=gdb@sourceware.org \
--cc=heidegg@hotmail.com \
--cc=luis.machado@arm.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