This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: Attaching and inspecting crash with gdb
- From: "Eli Zaretskii" <eliz at gnu dot org>
- To: Devrim Erdem <devrim dot erdem at gmail dot com>
- Cc: gdb at sources dot redhat dot com
- Date: Tue, 02 Nov 2004 21:14:26 +0200
- Subject: Re: Attaching and inspecting crash with gdb
- References: <ba9d84630411010303944c237@mail.gmail.com> <01c4c057$Blat.v2.2.2$c306b160@zahav.net.il> <ba9d846304110206473dfc3a5@mail.gmail.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
[Please don't remove the mailing list from the addressees.]
> Date: Tue, 2 Nov 2004 15:47:06 +0100
> From: Devrim Erdem <devrim.erdem@gmail.com>
>
> I agree that a core dump would be great.
>
> But, my customer is using a Redhat system which doesn't by default
> write any core dumps. Additionally, neither I nor they can tweak the
> system to enable core writing. (Don't know how to do. )
>
> If somebody knows how to enable core dumps without admin permissions
> or sys. tweak, I would be glad to try.
In my experience, it is usually a shell setting, so e.g. a command
such as ulimit should solve this.