All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Permes <christoph.permes@domain.hid>
To: xenomai@xenomai.org
Subject: [Xenomai-help] No core files for segmentation faults in realtime tasks
Date: Mon, 24 Aug 2009 10:07:47 +0200	[thread overview]
Message-ID: <1251101267.3754.18.camel@domain.hid> (raw)

Hi,

I have a realtime application running in user space that sometimes terminates with a segmentation fault. 
I get a message segfault at 4c4f5200 ip b7cb98d8 sp b7ef7354 error 4 in libc-2.7.so[b7c5e000+138000], 
but there is no core file writen, although ulimit is set to unlimited.

I wrote a small test program that produces a segmentation fault and I get a core file when the segfault
happens before the realtime task starts but not when it happens in the task.

Is it somehow possible to enable writing core files also for realtime tasks?

Thanks, 
Christoph




             reply	other threads:[~2009-08-24  8:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-24  8:07 Christoph Permes [this message]
2009-08-24  8:40 ` [Xenomai-help] No core files for segmentation faults in realtime tasks Philippe Gerum
2009-08-25  8:10   ` Christoph Permes
2009-08-24  8:50 ` Gilles Chanteperdrix

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=1251101267.3754.18.camel@domain.hid \
    --to=christoph.permes@domain.hid \
    --cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.