From: gshan <gshan@alcatel-lucent.com>
To: Willy Tarreau <w@1wt.eu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to produce a core
Date: Thu, 24 May 2007 12:23:17 +0800 [thread overview]
Message-ID: <46551335.7030909@alcatel-lucent.com> (raw)
In-Reply-To: <20070524034913.GN943@1wt.eu>
Willy Tarreau wrote:
> On Thu, May 24, 2007 at 11:28:15AM +0800, gshan wrote:
>
>> This morning, I tried command "kill -7 [pid]" but didn't see the core
>> file. Anybody has ideas?
>>
>
> do the following before starting your program :
>
> # ulimit -c unlimited
>
> You can check before and after that the core size changed from 0 to
> "unlimited" :
>
> # ulimit -a
>
> Willy
>
>
Willy,
Thank you very much. The command "kill -7 [pid]" really works with
"ulimit -c unlimited"
# /bin/sh
# ps
PID USER COMMAND
1 0 init
2 0 [ksoftirqd/0]
3 0 [desched/0]
4 0 [events/0]
5 0 [khelper]
10 0 [kthread]
31 0 [kblockd/0]
60 0 [pdflush]
61 0 [pdflush]
63 0 [aio/0]
62 0 [kswapd0]
64 0 [jfsIO]
65 0 [jfsCommit]
66 0 [jfsSync]
67 0 [xfslogd/0]
68 0 [xfsdatad/0]
69 0 [xfsbufd]
706 0 [mtdblockd]
730 0 -sh
788 0 /bin/sh
789 0 ps
# ulimit -c unlimited
# kill -7 788
Bus error (core dumped)
# ls -al
drwxr-xr-x 12 0 0 0 Jan 1 00:55 .
drwxr-xr-x 12 0 0 0 Jan 1 00:55 ..
drwxr-xr-x 2 1000 1000 0 Jan 1 00:00 bin
-rw------- 1 0 0 417792 Jan 1 00:55
core <<< Here is the corefile
drwxr-xr-x 2 0 0 0 Jan 1 00:00 dev
drwxr-xr-x 3 0 0 0 Jan 1 00:00 etc
lrwxrwxrwx 1 0 0 12 Jan 1 00:00 init -> /bin/busybox
drwxr-xr-x 2 0 0 0 Jan 1 00:00 lib
drwxr-xr-x 2 0 0 0 Jan 1 00:00 misc
dr-xr-xr-x 32 0 0 0 Jan 1 00:00 proc
drwx------ 2 0 0 0 Jan 1 00:00 root
drwxr-xr-x 2 0 0 0 Jan 1 00:00 sbin
drwxr-xr-x 2 0 0 0 Jan 1 00:00 sys
drwxr-xr-x 4 0 0 0 Jan 1 00:00 usr
#
Thanks,
Gavin
prev parent reply other threads:[~2007-05-24 4:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-24 3:28 How to produce a core gshan
2007-05-24 3:49 ` Willy Tarreau
2007-05-24 4:23 ` gshan [this message]
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=46551335.7030909@alcatel-lucent.com \
--to=gshan@alcatel-lucent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=w@1wt.eu \
/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.