public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Stan Cox <scox@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] consolidate gdbserver global data
Date: Wed, 25 Nov 2015 19:05:00 -0000	[thread overview]
Message-ID: <n34r5m$nis$1@ger.gmane.org> (raw)
In-Reply-To: <5648B89D.3050305@redhat.com>

Any thoughts/comments on this patch that consolidates gdbserver external 
data as shown in this example?

(gdb) print *cs
$2 = {server_waiting_ = 0,
   extended_protocol_ = 1, response_needed_ = 1, exit_requested_ = 0, 
run_once_ = 0, multi_process_ = 1, report_fork_events_ = 1,
   report_vfork_events_ = 1, non_stop_ = 1, swbreak_feature_ = 1, 
hwbreak_feature_ = 1, disable_randomization_ = 1,
   program_argv_ = 0x682840, wrapper_argv_ = 0x0, packet_length_ = 16, 
pass_signals_ =     {0 <repeats 14 times>,
   in_buffer_ = 0x6833c0 "vCont;t:p6feb.-1ו\225\225\225\225", 
<incomplete sequence \327>, own_buffer_ = 0x689fa0 "OK",
   client_breakpoints = 0x0, ss = 0x680430, next = 0x0}

(gdb) print *cs->ss
$3 = {attach_count_ = 1, cont_thread_ = {pid = 0, lwp = 0, tid = 0}, 
general_thread_ = {pid = 28651, lwp = 28651, tid = 0},
   signal_pid_ = 28651, last_status_ = {kind = 
TARGET_WAITKIND_NO_RESUMED, value = {integer = 5, sig = GDB_SIGNAL_TRAP,
       related_pid = {pid = 5, lwp = 0, tid = 0}, execd_pathname = 0x5,
       syscall_number = 5}}, last_ptid_ = {pid = 0, lwp = 0, tid = 0},
   mem_buf_ = 0x67bc70 ,
   readchar_buf_ =  "$vCont;t:p6feb.-1#52:64bit-avx.xml:",
   readchar_bufp_ = 0x6804c4 ":64bit-avx.xml:0,fff#1bfc;",
   all_processes_ = {head = 0x682a80, tail = 0x682a80},
   all_threads_ = {head = 0x682cb0, tail = 0x682cb0},
   current_thread_ = 0x682cb0}


  reply	other threads:[~2015-11-25 19:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-15 16:53 Stan Cox
2015-11-25 19:05 ` Stan Cox [this message]
2015-12-17 21:06   ` [PATCH v2 1/2] " Stan Cox
2015-12-17 21:15   ` [PATCH v2 2/2] " Stan Cox
2015-12-21 13:30     ` Pedro Alves
2015-12-21 17:04       ` Stan Cox

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='n34r5m$nis$1@ger.gmane.org' \
    --to=scox@redhat.com \
    --cc=gdb-patches@sourceware.org \
    /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).