Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Grant Edwards <grante@visi.com>
To: Ian Lance Taylor <ian@wasabisystems.com>
Cc: gdb@sources.redhat.com
Subject: Re: How to tell gdb to exit?
Date: Thu, 06 May 2004 18:42:00 -0000	[thread overview]
Message-ID: <20040506184211.GA13750@grante.dsl.visi.com> (raw)
In-Reply-To: <m3oep1bdy6.fsf@gossamer.airs.com>


>> I messed around with this on and off for days, and couldn't
>> find the answer, but as soon as I put my foot in my mouth
>> publically, the answer appears.  Odd, that.
> 
> I actually find that this is a fairly effective technique for solving
> a problem.  Send out a message, and then the answer occurs to you.
> The more people to whom you send the message, the more likely you are
> to find the answer yourself.

One might think that the answer should occur while one is
composing the message -- trying to explain the problem in
sufficient detail for others to understand often sometimes
reveals a solution.  While this does happen, it also seems that
at least as often the answer appears about 20 minutes later.

> I've learned to exploit this fact by composing the message but
> delaying the actual sending for a period of time.  Sometimes the
> answer will come to me before the message actually goes out.

I should try that...

-- 
Grant Edwards
grante@visi.com


  reply	other threads:[~2004-05-06 18:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-06 15:50 Grant Edwards
2004-05-06 16:09 ` Grant Edwards
2004-05-06 16:16   ` Grant Edwards
2004-05-06 16:18     ` Daniel Jacobowitz
2004-05-06 16:35       ` Grant Edwards
2004-05-06 19:14         ` Daniel Jacobowitz
2004-05-06 18:36     ` Ian Lance Taylor
2004-05-06 18:42       ` Grant Edwards [this message]
2004-05-06 16:10 ` Daniel Jacobowitz
2004-05-06 16:11   ` Grant Edwards

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=20040506184211.GA13750@grante.dsl.visi.com \
    --to=grante@visi.com \
    --cc=gdb@sources.redhat.com \
    --cc=ian@wasabisystems.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