From: "William A. Gatliff" <bgat@billgatliff.com>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: gdb-5.2.1 loses command line
Date: Wed, 04 Dec 2002 19:12:00 -0000 [thread overview]
Message-ID: <20021204211535.C31284@saturn.billgatliff.com> (raw)
In-Reply-To: <15854.49047.135664.970802@localhost.redhat.com>; from ezannoni@redhat.com on Wed, Dec 04, 2002 at 09:53:11PM -0500
Elena:
On Wed, Dec 04, 2002 at 09:53:11PM -0500, Elena Zannoni wrote:
> William A. Gatliff writes:
> > Guys:
> >
> >
>
> Hmmm this smells like async/event loop/signal handling problems. Can
> you try the same but after starting the debugger with --noasync? (if
> the --noasync is still there, that is... and if the noasync code
> hasn't bitrotted)
It appears to still be there, and it appears to have no affect.
b.g.
--
Bill Gatliff
I'm an embedded GNU developer first, GNU instructor second.
http://billgatliff.com
next prev parent reply other threads:[~2002-12-05 3:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-04 18:45 William A. Gatliff
2002-12-04 18:57 ` Elena Zannoni
2002-12-04 19:12 ` William A. Gatliff [this message]
2002-12-04 19:35 ` Elena Zannoni
2002-12-05 9:10 ` gdb-5.2.1 loses command line (fixed, sorta) William A. Gatliff
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=20021204211535.C31284@saturn.billgatliff.com \
--to=bgat@billgatliff.com \
--cc=ezannoni@redhat.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