Mirror of the gdb mailing list
 help / color / mirror / Atom feed
* Huge pages and gdb
@ 2011-03-23  8:45 Erez Zilber
  2011-03-23 17:09 ` Andreas Schwab
  0 siblings, 1 reply; 4+ messages in thread
From: Erez Zilber @ 2011-03-23  8:45 UTC (permalink / raw)
  To: gdb

Hi,

My application (running on RHEL 6) calls mmap() to map huge pages.
After it crashed, I opened gdb with the core file and tried to take a
look in the huge-pages buffer that was mmapped. I got the following
error:

gdb) p pool->mem
$2 = 0x7f3201400000 <Address 0x7f3201400000 out of bounds>
(gdb) p pool->mem[0]
Cannot access memory at address 0x7f3201400000

How can I solve this so I will be able to view the contents of the buffer?

Thanks,
Erez


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Huge pages and gdb
  2011-03-23  8:45 Huge pages and gdb Erez Zilber
@ 2011-03-23 17:09 ` Andreas Schwab
  2011-03-23 17:14   ` Jan Kratochvil
  0 siblings, 1 reply; 4+ messages in thread
From: Andreas Schwab @ 2011-03-23 17:09 UTC (permalink / raw)
  To: Erez Zilber; +Cc: gdb

Erez Zilber <erezzi.list@gmail.com> writes:

> My application (running on RHEL 6) calls mmap() to map huge pages.
> After it crashed, I opened gdb with the core file and tried to take a
> look in the huge-pages buffer that was mmapped. I got the following
> error:
>
> gdb) p pool->mem
> $2 = 0x7f3201400000 <Address 0x7f3201400000 out of bounds>
> (gdb) p pool->mem[0]
> Cannot access memory at address 0x7f3201400000

If gdb cannot access the memory then it is not part of the core file.
Please check with "info target" whether one of the segments cover the
address range.  If not, then either the address really is invalid, or it
is an issue with the core producer and gdb cannot do anything about
that.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Huge pages and gdb
  2011-03-23 17:09 ` Andreas Schwab
@ 2011-03-23 17:14   ` Jan Kratochvil
  2011-03-27  7:45     ` Erez Zilber
  0 siblings, 1 reply; 4+ messages in thread
From: Jan Kratochvil @ 2011-03-23 17:14 UTC (permalink / raw)
  To: Erez Zilber; +Cc: gdb, Andreas Schwab

On Wed, 23 Mar 2011 18:09:47 +0100, Andreas Schwab wrote:
> Erez Zilber <erezzi.list@gmail.com> writes:
> > (gdb) p pool->mem[0]
> > Cannot access memory at address 0x7f3201400000
> 
> If gdb cannot access the memory then it is not part of the core file.

And which pages are / are not dumped to the core file you can configure by:
/usr/share/doc/kernel-doc-*/Documentation/filesystems/proc.txt
  3.4   /proc/<pid>/coredump_filter - Core dump filtering settings


Regards,
Jan


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Huge pages and gdb
  2011-03-23 17:14   ` Jan Kratochvil
@ 2011-03-27  7:45     ` Erez Zilber
  0 siblings, 0 replies; 4+ messages in thread
From: Erez Zilber @ 2011-03-27  7:45 UTC (permalink / raw)
  To: Jan Kratochvil; +Cc: gdb, Andreas Schwab

On Wed, Mar 23, 2011 at 7:14 PM, Jan Kratochvil
<jan.kratochvil@redhat.com> wrote:
> On Wed, 23 Mar 2011 18:09:47 +0100, Andreas Schwab wrote:
>> Erez Zilber <erezzi.list@gmail.com> writes:
>> > (gdb) p pool->mem[0]
>> > Cannot access memory at address 0x7f3201400000
>>
>> If gdb cannot access the memory then it is not part of the core file.
>
> And which pages are / are not dumped to the core file you can configure by:
> /usr/share/doc/kernel-doc-*/Documentation/filesystems/proc.txt
>  3.4   /proc/<pid>/coredump_filter - Core dump filtering settings
>
>
> Regards,
> Jan
>

Thanks!


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2011-03-27  7:45 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-03-23  8:45 Huge pages and gdb Erez Zilber
2011-03-23 17:09 ` Andreas Schwab
2011-03-23 17:14   ` Jan Kratochvil
2011-03-27  7:45     ` Erez Zilber

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox