public inbox for archer@sourceware.org
 help / color / mirror / Atom feed
From: Roland McGrath <roland@redhat.com>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>,
	utrace-devel@redhat.com, archer@sourceware.org
Subject: Re: gdbstub initial code, v7
Date: Fri, 10 Sep 2010 10:15:00 -0000	[thread overview]
Message-ID: <20100910101452.39015405D5@magilla.sf.frob.com> (raw)
In-Reply-To: Oleg Nesterov's message of  Saturday, 4 September 2010 01:09:57 +0200 <20100903230957.GC8917@redhat.com>

> But I meant another case, when the stopped tracee doesn't have siginfo.
> Currently ugdb just sends this signal to tracee, and then it will be
> reported to gdb. Not sure if this is right or not, I can change this.
> (or perhap this doesn't matter, I dunno).

What do you mean by "doesn't have siginfo"?  You mean non-signal stops?
What non-signal stops does ugdb report?


Thanks,
Roland

  reply	other threads:[~2010-09-10 10:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-30 19:02 Oleg Nesterov
2010-08-30 19:20 ` Jan Kratochvil
2010-08-31  7:21   ` Jan Kratochvil
2010-09-02 20:09     ` Oleg Nesterov
2010-09-03  6:40       ` Jan Kratochvil
2010-09-03 19:59         ` Roland McGrath
2010-09-03 20:03           ` Jan Kratochvil
2010-09-03 20:10             ` Roland McGrath
2010-09-03 23:13         ` Oleg Nesterov
2010-09-10 10:15           ` Roland McGrath [this message]
2010-09-10 18:32             ` Oleg Nesterov
2010-09-10 19:06               ` Roland McGrath
2010-09-10 19:23                 ` Oleg Nesterov
2010-10-13  7:23                   ` Roland McGrath
2010-10-15 14:32                     ` Oleg Nesterov
2010-09-03 14:17       ` Frank Ch. Eigler
2010-09-03 23:00         ` Oleg Nesterov

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=20100910101452.39015405D5@magilla.sf.frob.com \
    --to=roland@redhat.com \
    --cc=archer@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=oleg@redhat.com \
    --cc=utrace-devel@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).