Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Paul Mundt <paul.mundt@timesys.com>
Cc: gdb@sources.redhat.com
Subject: Re: Gdbserver Threading Issues
Date: Fri, 06 Dec 2002 13:35:00 -0000	[thread overview]
Message-ID: <20021206213613.GA12321@nevyn.them.org> (raw)
In-Reply-To: <1039214262.11721.109.camel@Origin>

On Fri, Dec 06, 2002 at 05:37:43PM -0500, Paul Mundt wrote:
> On Fri, 2002-12-06 at 16:23, Daniel Jacobowitz wrote:
> > Look at set remote debug 1.  What's going on?
> > 
> My gdb doesn't seem to have that option:
> 
> (gdb) set remote debug 1
> Undefined set remote command: "debug 1".  Try "help set remote".
> 
> (gdb) help set remote
> Remote protocol specific variables
> Configure various remote-protocol specific variables such as
> the packets being used
> 
> List of set remote subcommands:
> 
> set remote P-packet -- Set use of remote protocol `P' (set-register)
> packet
> set remote X-packet -- Set use of remote protocol `X' (binary-download)
> packet
> set remote Z-packet -- Set use of remote protocol `Z' packets
> set remote access-watchpoint-packet -- Set use of remote protocol `Z4'
> (access-watchpoint) packet
> set remote binary-download-packet -- Set use of remote protocol `X'
> (binary-download) packet
> set remote hardware-breakpoint-packet -- Set use of remote protocol `Z1'
> (hardware-breakpoint) packet
> set remote memory-read-packet-size -- Set the maximum number of bytes
> per memory-read packet
> set remote memory-write-packet-size -- Set the maximum number of bytes
> per memory-write packet
> set remote read-watchpoint-packet -- Set use of remote protocol `Z3'
> (read-watchpoint) packet
> set remote set-register-packet -- Set use of remote protocol `P'
> (set-register) packet
> set remote software-breakpoint-packet -- Set use of remote protocol `Z0'
> (software-breakpoint) packet
> set remote step-over-range-packet -- Set use of remote protocol `e'
> (step-over-range) packet
> set remote step-over-range-w-signal-packet -- Set use of remote protocol
> `E' (step-over-range-w-signal) packet
> set remote symbol-lookup-packet -- Set use of remote protocol `qSymbol'
> (symbol-lookup) packet
> set remote write-watchpoint-packet -- Set use of remote protocol `Z2'
> (write-watchpoint) packet
> 
> Type "help set remote" followed by set remote subcommand name for full 
> documentation.
> 
> Is there a build option I need turned on to use this?

Sorry.  Set debug remote 1.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-12-06 21:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-06 11:20 Paul Mundt
2002-12-06 11:28 ` Daniel Jacobowitz
2002-12-06 13:07   ` Paul Mundt
2002-12-06 13:16     ` Daniel Jacobowitz
2002-12-06 13:20       ` Paul Mundt
2002-12-06 13:23         ` Daniel Jacobowitz
2002-12-06 13:33           ` Paul Mundt
2002-12-06 13:35             ` Daniel Jacobowitz [this message]
2002-12-06 13:59           ` Paul Mundt
2002-12-06 14:08             ` Daniel Jacobowitz
2002-12-06 14:15               ` Paul Mundt
2002-12-06 17:15                 ` Daniel Jacobowitz

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=20021206213613.GA12321@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb@sources.redhat.com \
    --cc=paul.mundt@timesys.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