From: "Eli Zaretskii" <eliz@gnu.org>
To: Devrim Erdem <devrim.erdem@gmail.com>
Cc: gdb@sources.redhat.com
Subject: Re: Attaching and inspecting crash with gdb
Date: Mon, 01 Nov 2004 21:20:00 -0000 [thread overview]
Message-ID: <01c4c057$Blat.v2.2.2$c306b160@zahav.net.il> (raw)
In-Reply-To: <ba9d84630411010303944c237@mail.gmail.com> (message from Devrim Erdem on Mon, 1 Nov 2004 12:03:58 +0100)
> Date: Mon, 1 Nov 2004 12:03:58 +0100
> From: Devrim Erdem <devrim.erdem@gmail.com>
>
> Classic problem. Customer uses software heavily. Software crashes from
> time to time. No core dumps.
Why ``no core dumps''? It's easier to cause them than to look for
other solutions, in my experience. Then the customer could send you
the core file, and you could debug the problem at your place.
next prev parent reply other threads:[~2004-11-01 21:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-01 11:04 Devrim Erdem
2004-11-01 11:34 ` Marco Molteni
2004-11-01 14:07 ` Daniel Jacobowitz
2004-11-01 14:26 ` Devrim Erdem
2004-11-01 21:20 ` Eli Zaretskii [this message]
[not found] ` <ba9d846304110206473dfc3a5@mail.gmail.com>
2004-11-02 19:21 ` Eli Zaretskii
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='01c4c057$Blat.v2.2.2$c306b160@zahav.net.il' \
--to=eliz@gnu.org \
--cc=devrim.erdem@gmail.com \
--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