public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Kris Warkentin <kewarken@qnx.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: GDB <gdb@sources.redhat.com>
Subject: Re: Possibly dumb signal mapping question
Date: Fri, 18 Mar 2005 15:00:00 -0000	[thread overview]
Message-ID: <423AED09.1080308@qnx.com> (raw)
In-Reply-To: <20050318145234.GA24185@nevyn.them.org>

Daniel Jacobowitz wrote:

>No, there isn't - you could do it in your remote protocol target (don't
>you
>use a different protocol?)
>

Yeah.  I just created some mapping functions to apply whenever the 
signal is sent or received on the wire.  It's in the remote part of our 
port that I haven't submitted yet.  I'm waiting for some time where I 
won't keep getting pre-empted.  It's annoying when I submit something to 
you guys and then can't devote my full attention to following up.

cheers,

Kris

      reply	other threads:[~2005-03-18 15:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-17 22:30 Kris Warkentin
2005-03-17 22:33 ` Daniel Jacobowitz
2005-03-18 14:47   ` Kris Warkentin
2005-03-18 14:53     ` Daniel Jacobowitz
2005-03-18 15:00       ` Kris Warkentin [this message]

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=423AED09.1080308@qnx.com \
    --to=kewarken@qnx.com \
    --cc=drow@false.org \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).