From: Joel Brobecker <brobecker@gnat.com>
To: "Bennett F. Dill" <bdill@linux.dillfamily.org>
Cc: gdb@sources.redhat.com
Subject: Re: core while attached
Date: Tue, 28 Jan 2003 03:51:00 -0000 [thread overview]
Message-ID: <20030128035147.GF6437@gnat.com> (raw)
In-Reply-To: <20030127183252.GA9690@linux.dillfamily.org>
> Anyway, the application runs in the background and is a server to about
> 25 clients concurrently. It takes a few hours for the app to sigsegv.
> Now, it never dumped a core for some reason, so i just attach gdb to the
> process and continue and wait for the error to rear its head.
Maybe your server is larger than a certain size and that past this size
the system elects not to dump a core file. I don't know on which system
you are running, but you can usually raise the limit by using utilities
like "ulimit", for instance "ulimit -c 100000" or somesuch.
--
Joel
next prev parent reply other threads:[~2003-01-28 3:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-27 18:31 Bennett F. Dill
2003-01-27 19:19 ` Daniel Jacobowitz
2003-01-27 19:44 ` Bennett F. Dill
2003-01-27 20:57 ` Bennett F. Dill
2003-01-27 21:02 ` Daniel Jacobowitz
2003-01-28 14:33 ` Bennett F. Dill
2003-01-28 3:51 ` Joel Brobecker [this message]
2003-01-28 14:31 ` Bennett F. Dill
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=20030128035147.GF6437@gnat.com \
--to=brobecker@gnat.com \
--cc=bdill@linux.dillfamily.org \
--cc=gdb@sources.redhat.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