From: Pedro Alves <palves@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Oleg Nesterov <oleg@redhat.com>,
Sergio Durigan Junior <sergiodj@redhat.com>,
GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Improve corefile generation by using /proc/PID/coredump_filter (PR corefile/16902)
Date: Thu, 12 Mar 2015 16:19:00 -0000 [thread overview]
Message-ID: <5501BC3A.2010608@redhat.com> (raw)
In-Reply-To: <20150312155712.GA1837@host1.jankratochvil.net>
On 03/12/2015 03:57 PM, Jan Kratochvil wrote:
> On Thu, 12 Mar 2015 16:45:15 +0100, Pedro Alves wrote:
>> On 03/12/2015 03:00 PM, Oleg Nesterov wrote:
>>
>>> However. If (for any reason) you decide to dump this region, gdb can
>>> look into /proc/self/maps, find its own "vvar" mapping, and simply read
>>> this memory. Unlike "vdso", "vvar" has the same content for every process.
>>
>> Actually it can't: GDB may well be dumping the memory of
>> a process running on another machine (through gdbserver).
>
> So it can - from gdbserver's [vvar].
Sure, but GDB is just remotely reading the /proc files.
We'd need a new RSP packet to get at that object. All
for working around something that sounds like the kernel
should be supporting without hacks.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2015-03-12 16:19 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 3:48 Sergio Durigan Junior
2015-03-05 15:48 ` Jan Kratochvil
2015-03-05 20:53 ` Sergio Durigan Junior
2015-03-05 20:57 ` Jan Kratochvil
2015-03-11 20:02 ` Oleg Nesterov
2015-03-12 11:31 ` Sergio Durigan Junior
2015-03-12 14:36 ` vvar, gup && coredump Oleg Nesterov
2015-03-12 16:29 ` Andy Lutomirski
2015-03-12 16:56 ` Oleg Nesterov
2015-03-12 17:18 ` Andy Lutomirski
2015-03-12 17:40 ` Oleg Nesterov
2015-03-12 17:45 ` Sergio Durigan Junior
2015-03-12 18:04 ` Oleg Nesterov
2015-03-13 4:50 ` Sergio Durigan Junior
2015-03-13 15:06 ` Oleg Nesterov
2015-03-12 17:56 ` Andy Lutomirski
2015-03-12 18:28 ` Oleg Nesterov
2015-03-12 17:48 ` Oleg Nesterov
2015-03-12 17:55 ` Andy Lutomirski
2015-03-12 18:16 ` Oleg Nesterov
2015-03-12 18:23 ` Sergio Durigan Junior
2015-03-12 18:20 ` Pedro Alves
2015-03-12 18:26 ` Andy Lutomirski
2015-03-16 19:03 ` install_special_mapping && vm_pgoff (Was: vvar, gup && coredump) Oleg Nesterov
2015-03-16 19:20 ` Andy Lutomirski
2015-03-16 19:46 ` Oleg Nesterov
2015-03-17 13:45 ` Oleg Nesterov
2015-03-18 1:45 ` Andy Lutomirski
2015-03-18 18:08 ` Oleg Nesterov
2015-03-16 19:40 ` Pedro Alves
2015-03-12 15:02 ` [PATCH] Improve corefile generation by using /proc/PID/coredump_filter (PR corefile/16902) Oleg Nesterov
2015-03-12 15:46 ` Pedro Alves
2015-03-12 15:57 ` Jan Kratochvil
2015-03-12 16:19 ` Pedro Alves [this message]
2015-03-12 16:07 ` Oleg Nesterov
2015-03-12 16:28 ` Pedro Alves
2015-03-12 17:37 ` Sergio Durigan Junior
2015-03-12 21:39 ` [PATCH v2] " Sergio Durigan Junior
2015-03-13 19:34 ` Pedro Alves
2015-03-16 23:53 ` Sergio Durigan Junior
2015-03-18 19:10 ` Pedro Alves
2015-03-18 19:39 ` Sergio Durigan Junior
2015-03-14 9:40 ` Eli Zaretskii
2015-03-16 2:42 ` Sergio Durigan Junior
2015-03-13 19:37 ` [PATCH] " Pedro Alves
2015-03-13 19:48 ` Pedro Alves
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=5501BC3A.2010608@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=oleg@redhat.com \
--cc=sergiodj@redhat.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