From: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
To: drow@false.org
Cc: gdb-patches@sources.redhat.com
Subject: Re: remote debugging a multi-threaded program with signal
Date: Fri, 19 Mar 2004 00:09:00 -0000 [thread overview]
Message-ID: <20040307.232138.74755320.anemo@mba.ocn.ne.jp> (raw)
Message-ID: <20040319000900.IedRMi1KKKWHwAGC4q_NJsjzZZ4wAHXXslVZ57sZWxw@z> (raw)
In-Reply-To: <20040306171112.GA23154@nevyn.them.org>
>>>>> On Sat, 6 Mar 2004 12:11:13 -0500, Daniel Jacobowitz <drow@false.org> said:
>> Hmm... then it might be better to backport all vCont stuff? Of
>> course upgrading to upcoming gdb 6.1 will be the best solution, but
>> I can not for now by some internal reason ... :-\
drow> Yes, I would rather you backport vCont than we add hacks to
drow> gdbserver to guess :) I can tell you that the only changes to
drow> support vCont (as far as I remember, anyway) were in remote.c.
drow> It was pretty simple client-side.
Thanks for your suggestion. I'll try to do it.
---
Atsushi Nemoto
next prev parent reply other threads:[~2004-03-07 14:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-03 15:59 Atsushi Nemoto
2004-03-19 0:09 ` Atsushi Nemoto
2004-03-04 14:58 ` Atsushi Nemoto
2004-03-04 22:28 ` Daniel Jacobowitz
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-19 0:09 ` Atsushi Nemoto
2004-03-05 4:15 ` Atsushi Nemoto
2004-03-19 0:09 ` Atsushi Nemoto
2004-03-05 2:25 ` Atsushi Nemoto
2004-03-19 0:09 ` Atsushi Nemoto
2004-03-05 16:36 ` Atsushi Nemoto
2004-03-05 16:38 ` Daniel Jacobowitz
2004-03-06 12:42 ` Atsushi Nemoto
2004-03-19 0:09 ` Atsushi Nemoto
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-06 17:11 ` Daniel Jacobowitz
2004-03-07 14:14 ` Atsushi Nemoto [this message]
2004-03-19 0:09 ` Atsushi Nemoto
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-19 0:09 ` Atsushi Nemoto
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=20040307.232138.74755320.anemo@mba.ocn.ne.jp \
--to=anemo@mba.ocn.ne.jp \
--cc=drow@false.org \
--cc=gdb-patches@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