From: "Stanley Gambarin" <stanley@apogee.com>
To: <a2782@dis.ulpgc.es>, <gdb@sources.redhat.com>
Subject: Re: Pipe question (mmm)
Date: Thu, 05 Dec 2002 10:56:00 -0000 [thread overview]
Message-ID: <02Dec5.103725pst.119042@gateway.apogee.com> (raw)
In-Reply-To: <200212042225.gB4MPEq04369@siglo21.dis.ulpgc.es>
it is unlikely that sending \"quit\\n\" down to GDB will work,
since it will take some time for GDB to reply to 'quit' command.
The solution that work for me (in a very similar situation), is to
issue following commands:
> set confirm off
> quit
The 'confirm' command is used to confirm dangerous operations;
disabling it will tell GDB to just go ahead and quit (killing inferior, if
there is one present).
Hope that helps,
-- stanley
----- Original Message -----
From: <a2782@dis.ulpgc.es>
To: <gdb@sources.redhat.com>
Sent: Wednesday, December 04, 2002 2:25 PM
Subject: Re: Pipe question (mmm)
> Thanks again to Eli (I have removed the bug of strcat and the constant
> string) and Michael C for their effort.
>
> It\'s important to realize that gdb asks to confirm in several points of
> its execution (I will consider it from now). But I was using a very
> short code and this prompt didn\'t appear (and, as I said, GDB is ending
> properly). I wonder if it can be a problem with my development GUI
> (Kylix 3.0 Open Edition) or something I may be missing. Well, if anyone
> knows something new, don\'t hesitate to help me!
>
> Ciao!
>
next prev parent reply other threads:[~2002-12-05 18:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-04 8:45 Pipe question Michael Elizabeth Chastain
2002-12-04 13:27 ` Pipe question (mmm) a2782
2002-12-05 10:56 ` Stanley Gambarin [this message]
[not found] ` <02Dec5.103736pst.119043@gateway.apogee.com>
2002-12-06 8:58 ` a2782
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=02Dec5.103725pst.119042@gateway.apogee.com \
--to=stanley@apogee.com \
--cc=a2782@dis.ulpgc.es \
--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