From: "Кукушкин Павел Геннадьевич" <kukp@1c.ru>
To: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Minimal core dump mapping set
Date: Wed, 20 Apr 2016 17:00:00 -0000 [thread overview]
Message-ID: <dc359f2a-ac3f-4619-b4f7-1e515af60989@sourceware.org> (raw)
Dear developers,
I want to generate core dump file by application itself. Of course it supposed to be compatible with gdb. When I store all anonymous mappings to the file I get no problems. I can see stacks and heaps and so forth. But I want to store only stacks without heap. So I decided to skip anonymous mappings. Here I get in trouble. Gdb can't open that kind of core. I noticed that storing last 4 anonymous mappings (I mean in proc maps list) solves the problem. But how can I be sure that and if the particular mapping is vital for gdb. And what do those mappings keep.
Thank you for answer,
Pavel Kukushkin,
kukp@1c.ru
next reply other threads:[~2016-04-20 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-20 17:00 Кукушкин Павел Геннадьевич [this message]
2016-04-22 5:25 ` vijay nag
2016-04-27 18:39 ` Antoine Tremblay
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=dc359f2a-ac3f-4619-b4f7-1e515af60989@sourceware.org \
--to=kukp@1c.ru \
--cc=gdb@sourceware.org \
/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