From: Amol Lad <amol.lad@gmail.com>
To: gdb@sourceware.org
Subject: GDB bt command and core dumps
Date: Tue, 24 Mar 2009 14:28:00 -0000 [thread overview]
Message-ID: <8c675e9b0903240728i7e044580yae1deff480b3ffc9@mail.gmail.com> (raw)
Hi,
I'm working on an ARM9 platform (running Linux 2.6.18) and using gdb
6.6 compiled for the platform. My application is a multithreaded
application and on a crash it generates core of around 200MByte. I'm
looking to reduce the size of the core file and I _only_ need gdb 'bt'
command output ; no other debugging information (i.e I'm only
interested in the call trace)
- I tried ulimit -c command but the core produced are not useful in most cases
- I changed kernels fs/binfmt_elf.c file and modified maydump function
to just add crashed thread's stack in the core but no success
What all information should be present in the core file so that bt
output works reliably. Is stack of crashed thread not enough ? My
application is compiled with -O2 (hence -fomit-frame-pointer)
Thanks
--
Amol
Sent from: Bangalore KA India.
next reply other threads:[~2009-03-24 14:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 14:28 Amol Lad [this message]
2009-03-24 14:42 ` Daniel Jacobowitz
2009-03-25 7:12 ` Amol Lad
2009-03-25 10:48 ` Amol Lad
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=8c675e9b0903240728i7e044580yae1deff480b3ffc9@mail.gmail.com \
--to=amol.lad@gmail.com \
--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