All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zdenek Kabelac <kabi@i.am>
To: unlisted-recipients:; (no To-header on input)@localhost.localdomain
Subject: Kernel doesn't create core for threads
Date: Wed, 2 May 2001 20:53:00 GMT	[thread overview]
Message-ID: <3AF073AC.AE48BB78@i.am> (raw)

Hello

Looks to me like the latest 2.4.5-pre1 is not creating
coredump for multithreaded aplications:

----
$ ulimit  -a
core file size (blocks)     unlimited
data seg size (kbytes)      unlimited
file size (blocks)          unlimited
max locked memory (kbytes)  unlimited
max memory size (kbytes)    unlimited
open files                  1024
pipe size (512 bytes)       8
stack size (kbytes)         8192
cpu time (seconds)          unlimited
max user processes          6144
virtual memory (kbytes)     unlimited

$ ./testcore 
Segmentation fault


--- test program --

#include <stdio.h>
#include <pthread.h>

#define TASKS 10

void* thread(void* arg)
{
    printf("yuk %s\n", 0xffff0000);
    return 0;
}

int main(int argc, char *argv[])
{
    pthread_t task[TASKS];
    void* ret;
    int i = 0;
    for(i = 0; i < TASKS; i++)
	pthread_create(&task[i], NULL, thread, 0);
    for(i = 0; i < TASKS; i++)
	pthread_join(task[i], &ret);

    return 0;
}
---


for single threadad apps there is no problem:
(just put printf after int i declaration)
$ ./testcore 
Segmentation fault (core dumped)

---

Am I doing something wrong ???

Also for quite a long time Alan's AC patches were efictively locking
my machine when threaded application was crashing - resolvin
almost original behaviour solved this problem - but I like 
per-thread coredump - is there any special reason why this is still
not present in the current 2.4.4 kernel as I can see this as quite
usefull.


bye


kabi@i.am


             reply	other threads:[~2001-05-02 20:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-02 20:53 Zdenek Kabelac [this message]
2001-05-02 21:03 ` Kernel doesn't create core for threads Don Dugger

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=3AF073AC.AE48BB78@i.am \
    --to=kabi@i.am \
    /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.