Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] No core dump when killed with ABRT, SEGV, etc.
Date: Tue, 26 Mar 2013 16:25:54 +0000 (UTC)	[thread overview]
Message-ID: <kisi6i$srj$1@ger.gmane.org> (raw)

I get a proper core dump if a program actually causes a segfault, but
I can't figure out how to force a coredump by killing a running
process.

On my desktop machines with glibc, this generates a core dump:

tty1:

   $ ulimit -c 9999999
   $ <start program>

tty2:    
   $ kill -ABRT <pid>
 
On my buildroot system, there's no core dump.  The program is aborted
as expected, but it doesn't dump a core file.  If the same program
tries to actually dereference a NULL pointer there is a core dump.

Why doesn't killing a process with SIGABRT or SIGSEGV cause a core
dump?

-- 
Grant Edwards               grant.b.edwards        Yow! I am covered with
                                  at               pure vegetable oil and I am
                              gmail.com            writing a best seller!

             reply	other threads:[~2013-03-26 16:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-26 16:25 Grant Edwards [this message]
2013-03-26 16:50 ` [Buildroot] No core dump when killed with ABRT, SEGV, etc Peter Korsgaard
2013-03-26 17:01   ` Grant Edwards

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='kisi6i$srj$1@ger.gmane.org' \
    --to=grant.b.edwards@gmail.com \
    --cc=buildroot@busybox.net \
    /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