From: Aleksandar Ristovski <aristovski@qnx.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH 0/8] v2 - validate binary before use
Date: Tue, 09 Apr 2013 18:09:00 -0000 [thread overview]
Message-ID: <51643750.7080608@qnx.com> (raw)
In-Reply-To: <20130409153643.GA25825@host2.jankratochvil.net>
On 13-04-09 11:36 AM, Jan Kratochvil wrote:
> On Tue, 09 Apr 2013 17:27:37 +0200, Aleksandar Ristovski wrote:
>> Core support:
>> - core will use second method. Note, however, that due to (at least
>> on ubuntu) not dumping page containing buid-id in the core, the
>> validation can not be performed (it will always default to valid).
>> This is misfortunate but outside the scope of this patch.
>
> FYI it is bit 4 in /proc/self/coredump_filter, Fedora has the default 0x33.
>
> It is configured for Linux kernel by:
> linux-2.6/fs/Kconfig.binfmt CORE_DUMP_DEFAULT_ELF_HEADERS
>
> One can simulate it if not pre-configured:
> echo 0x33 >/proc/self/coredump_filter
>
Good to know. Thanks. In that case, it will be picked up by normal
target_read_memory (second method).
---
Aleksandar
next prev parent reply other threads:[~2013-04-09 15:44 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 16:15 Aleksandar Ristovski
2013-04-09 15:53 ` [PATCH 1/8] Move utility functions to common/ Aleksandar Ristovski
2013-04-09 16:01 ` [PATCH 2/8] Merge multiple hex conversions Aleksandar Ristovski
2013-04-09 16:03 ` [PATCH 3/8] Create empty common/linux-maps.[ch] and common/common-target.[ch] Aleksandar Ristovski
2013-04-15 13:34 ` Jan Kratochvil
2013-04-09 16:39 ` [PATCH 4/8] Prepare linux_find_memory_regions_full & co. for move Aleksandar Ristovski
2013-04-15 13:36 ` Jan Kratochvil
2013-04-16 17:19 ` Aleksandar Ristovski
2013-04-09 16:48 ` [PATCH 5/8] Move linux_find_memory_regions_full & co Aleksandar Ristovski
2013-04-15 13:52 ` Jan Kratochvil
2013-04-16 15:46 ` Aleksandar Ristovski
2013-04-09 16:55 ` [PATCH 6/8] gdbserver build-id attribute generator Aleksandar Ristovski
2013-04-09 18:52 ` Eli Zaretskii
2013-04-15 14:23 ` Jan Kratochvil
2013-04-16 16:40 ` Aleksandar Ristovski
2013-04-18 10:08 ` Jan Kratochvil
2013-04-09 17:37 ` [PATCH 8/8] Tests for validate symbol file using build-id Aleksandar Ristovski
2013-04-15 15:12 ` Jan Kratochvil
2013-04-16 17:25 ` Aleksandar Ristovski
2013-04-18 5:37 ` Jan Kratochvil
2013-04-09 17:50 ` [PATCH 7/8] Validate " Aleksandar Ristovski
2013-04-10 22:35 ` Aleksandar Ristovski
2013-04-10 19:58 ` Aleksandar Ristovski
2013-04-11 1:26 ` Jan Kratochvil
2013-04-11 2:43 ` Aleksandar Ristovski
2013-04-15 14:58 ` Jan Kratochvil
2013-04-16 19:14 ` Aleksandar Ristovski
2013-04-18 10:23 ` Jan Kratochvil
2013-04-09 17:53 ` [PATCH 0/8] v2 - validate binary before use Jan Kratochvil
2013-04-09 18:09 ` Aleksandar Ristovski [this message]
2013-04-16 18:03 ` Aleksandar Ristovski
2013-04-16 18:30 ` [PATCH 2/8] Merge multiple hex conversions Aleksandar Ristovski
2013-04-16 18:30 ` [PATCH 7/8] Validate symbol file using build-id Aleksandar Ristovski
2013-04-16 18:31 ` [PATCH 4/8] Prepare linux_find_memory_regions_full & co. for move Aleksandar Ristovski
2013-04-18 8:58 ` Jan Kratochvil
2013-04-16 18:31 ` [PATCH 1/8] Move utility functions to common/ Aleksandar Ristovski
2013-04-16 18:31 ` [PATCH 6/8] gdbserver build-id attribute generator Aleksandar Ristovski
2013-04-18 7:40 ` Jan Kratochvil
2013-04-16 18:31 ` [PATCH 8/8] Tests for validate symbol file using build-id Aleksandar Ristovski
2013-04-18 10:15 ` Jan Kratochvil
2013-04-16 18:31 ` [PATCH 5/8] Move linux_find_memory_regions_full & co Aleksandar Ristovski
2013-04-16 20:24 ` [PATCH 3/8] Create empty common/linux-maps.[ch] and common/common-target.[ch] Aleksandar Ristovski
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=51643750.7080608@qnx.com \
--to=aristovski@qnx.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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