From: "Breno" <brenosp@brasilsec.com.br>
To: <tim@cambrant.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Force Coredump
Date: Mon, 24 Nov 2003 11:48:10 -0200 [thread overview]
Message-ID: <002301c3b291$9a2f50a0$34dfa7c8@bsb.virtua.com.br> (raw)
In-Reply-To: <20031124133120.GA13678@cambrant.com>
Done , but no coredump file
%ulimit -c unlimited
%./test
Segmention fault
%ls -lisa
test* test.c
-----test.c ------
#include <stdio.h>
int main()
{
int *i = 0;
if(*i)
exit(1);
}
------------------
test is owned by the same user of directory
att,
Breno
----- Original Message -----
From: <tim@cambrant.com>
To: "Breno" <brenosp@brasilsec.com.br>
Cc: <linux-kernel@vger.kernel.org>
Sent: Monday, November 24, 2003 11:31 AM
Subject: Re: Force Coredump
> On Mon, Nov 24, 2003 at 11:15:51AM -0200, Breno wrote:
> > Anybody knows why ?
>
> Perhaps you don't have writing access to the directory where the program
is placed, or there is already a core file in the same directory, which you
don't have writing access to. Another possibility (more likely) is that
'ulimit -c' is set too low. Try typing 'ulimit -c unlimited' and see if that
works. This command will produce a core file for every segfault that occurs,
which may be inconvenient, so take a note of what ulimit is set to before
you change it.
>
> Hope that helps. Good luck.
>
> --
> Tim Cambrant <tim@cambrant.com>
> GPG KeyID 0x59518702
> Fingerprint: 14FE 03AE C2D1 072A 87D0 BC4D FA9E 02D8 5951 8702
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2003-11-24 13:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-24 13:15 Breno
2003-11-24 13:31 ` tim
2003-11-24 13:48 ` Breno [this message]
2003-11-24 15:13 ` Willy Tarreau
2003-11-24 14:06 ` Jan-Benedict Glaw
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='002301c3b291$9a2f50a0$34dfa7c8@bsb.virtua.com.br' \
--to=brenosp@brasilsec.com.br \
--cc=linux-kernel@vger.kernel.org \
--cc=tim@cambrant.com \
/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
all inboxes | Powered by JetHome®