public inbox for insight-prs@sourceware.org
help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: kseitz@sources.redhat.com
Cc: insight-prs@sources.redhat.com,
Subject: RE: insight/133: Remote debugging errors
Date: Fri, 22 Mar 2002 09:03:00 -0000	[thread overview]
Message-ID: <20020322170300.30389.qmail@sources.redhat.com> (raw)

The following reply was made to PR insight/133; it has been noted by GNATS.

From: Keith Seitz <keiths@redhat.com>
To: Christopher Dow <cdow@sonicblue.com>
Cc: "'insight-gnats@sources.redhat.com'" <insight-gnats@sources.redhat.com>
Subject: RE: insight/133: Remote debugging errors
Date: Fri, 22 Mar 2002 08:53:37 -0800 (PST)

 On Fri, 22 Mar 2002, Christopher Dow wrote:
 
 > When I tried that using Cygwin->Linux or Linux->Linux (using localhost:10001
 > as the port), it printed the message "Remote debugging using <name>:10001",
 > then never gave a prompt, and failed to come back at all.  Odd.
 
 Then this is definitely a backend bug. Here's what I would recommend...
 
 First, search the gdb mail archives to see if someone else has had this
 problem. If you find nothing, then I would capture the output of a gdb
 session (or cut and paste it) and either send it to gdb@sources.redhat.com
 (or submit a bug at http://sources.redhat.com/gdb). There are many more
 backend developers than gui developers.
 
 (You might want to add "set debug remote 1" to your session, too, for the
 gdb folks. This will give them real insight into the problem. (No pun
 intended!)
 
 Keith
 
 


             reply	other threads:[~2002-03-22 17:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-22  9:03 Keith Seitz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-03-22  9:04 kseitz
2002-03-22  8:43 Christopher Dow
2002-03-21 18:13 kseitz
2002-03-21 12:23 cdow

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=20020322170300.30389.qmail@sources.redhat.com \
    --to=keiths@redhat.com \
    --cc=insight-prs@sources.redhat.com \
    --cc=kseitz@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).