Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Dan Kegel <dank@kegel.com>
To: "Korbel, Michal" <Michal.Korbel@intel.com>
Cc: gdb@sources.redhat.com
Subject: Re: Thread Support for remote debugging
Date: Fri, 01 Feb 2002 08:27:00 -0000	[thread overview]
Message-ID: <3C5AC35B.5A9708DF@kegel.com> (raw)
In-Reply-To: <413FBB0BA5AED1119122000083234B1A01C74293@alpha.igk.intel.com>

Cool.  Can you post a patch, or an archive of your sources?
I'd like to link to it from http://www.kegel.com/linux/gdbserver.html
- Dan

"Korbel, Michal" wrote:
> 
> I was use source for gdbserver based on GDB 5.0,
> but I was add protocol support based on Quality Quorum source code
> (multithread and zbreak packet support)
> and move part of multithread support from GDB 5.0 core into gdbserver code.
> There are some bugs, but looks and work quite good.
> The most importent is: " we can start debug after all thread are created",
> there are problems with adding or deleting thread in internal thread list.
> ----------------------------------------------------------------------------
> ----------
> Michal Korbel - Software engineer
> Intel Technology Poland Sp. z o.o.; ul. Slowackiego 173; 80-298 Gdansk
> tel. +48 58 34-81-726; fax: +48 58 34-81-505; mobile:+48 603-203-142
> ----------------------------------------------------------------------------
> ----------
> 
> -----Original Message-----
> From: Dan Kegel [mailto:dank@kegel.com]
> Sent: Friday, February 01, 2002 4:51 PM
> To: Korbel, Michal
> Cc: 'Michael Snyder'; Sarnath K - CTD, Chennai.; gdb@sources.redhat.com
> Subject: Re: Thread Support for remote debugging
> 
> "Korbel, Michal" wrote:
> >
> > GDB have remote thread support and works fine with remote multithread
> > target,
> > to work with this feature you need have GDBSERVER with remote thread
> > support.
> > In the middle of 2001 I was build own version GDBSERVER with remote thread
> > support (x86-linux target only).
> > GDB (this version only) have only one restriction, the connection to
> remote
> > target can by start only from console window, but after first breakpoints
> we
> > can use all GDB features with full mouse support.
> 
> Now I'm really confused.  What source did you use for gdbserver?
> 
> - Dan


  reply	other threads:[~2002-02-01 16:27 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-01  8:13 Korbel, Michal
2002-02-01  8:27 ` Dan Kegel [this message]
2002-02-01  9:43   ` Quality Quorum
  -- strict thread matches above, loose matches on Subject: below --
2002-01-31 23:32 Korbel, Michal
2002-02-01  7:45 ` Dan Kegel
2002-01-21 22:08 Sarnath K - CTD, Chennai.
2002-01-21  1:11 Sarnath K - CTD, Chennai.
2002-01-21  6:07 ` Daniel Jacobowitz
2002-01-21  7:10 ` Quality Quorum
2002-01-21  8:38   ` Andrew Cagney
2002-01-31 12:47 ` Michael Snyder
2002-01-31 15:12   ` Daniel Jacobowitz
2002-01-31 15:22     ` Quality Quorum
2002-01-31 17:22       ` Daniel Jacobowitz
2002-01-31 19:41         ` Quality Quorum
2002-01-31 19:29       ` Andrew Cagney
2002-01-31 19:44         ` Quality Quorum
2002-01-31 15:41     ` Michael Snyder
2002-01-31 17:18       ` Daniel Jacobowitz
2002-01-31 17:21         ` Michael Snyder

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=3C5AC35B.5A9708DF@kegel.com \
    --to=dank@kegel.com \
    --cc=Michal.Korbel@intel.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