Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: FYI: gdbserver branch merges
Date: Fri, 29 Mar 2002 11:10:00 -0000	[thread overview]
Message-ID: <20020329141059.B12204@nevyn.them.org> (raw)

I've moved these patches to the branch.  This is all the gdbserver
changes except for x86-64 (which was too invasive, and I don't consider
urgent since x86-64 is not yet a production architecture) since we
branched.  For the signals code I created new files without removing
the old definitions.

gdb/:

2002-03-29  Daniel Jacobowitz  <drow@mvista.com>

        Merge from trunk:

        2002-03-27  Daniel Jacobowitz  <drow@mvista.com>

        * gdbserver/server.c (main): Call target_signal_to_host_p
        and target_signal_to_host on signals received from the remote.
        * gdbserver/remote-utils.c (prepare_resume_reply): Call
        target_signal_from_host on signals sent to the remote.
        * gdbserver/server.h: Add prototypes.  Include "gdb/signals.h".
        * gdbserver/Makefile.in: Add signals.o.  Add -I${INCLUDE_DIR}.


        2002-03-20  Martin M. Hunt  <hunt@redhat.com>

        * gdbserver/remote-utils.c (remote_open): Don't call
        getprotobyname, we're all using TCP here so just use
        IPPROTO_TCP.
        * gdbserver/gdbreplay.c (remote_open): Ditto.


        2002-03-13  Michal Ludvig  <mludvig@suse.cz>

        * gdbserver/remote-util.c (remote_open): Print remote-side's
        IP address when remote debugging over the network.

2002-03-29  Daniel Jacobowitz  <drow@mvista.com>

        Merge from trunk:
        2002-03-27  Daniel Jacobowitz  <drow@mvista.com>

        * signals/signals.c: Include "server.h" in gdbserver build.
        (target_signal_from_name): Don't use STREQ.
        (_initialize_signals): Likewise.  Don't include function in
        gdbserver build.

2002-03-29  Daniel Jacobowitz  <drow@mvista.com>

        Merge from trunk:
        * signals/signals.c: New file, copied from signals.c.

include/:
2002-03-29  Daniel Jacobowitz  <drow@mvista.com>

        Merge from trunk:
        2002-03-10  Daniel Jacobowitz <drow@mvista.com>
        * gdb: New directory.

include/gdb/:
2002-03-29  Daniel Jacobowitz  <drow@mvista.com>

        Merge from trunk:
        2002-03-10  Daniel Jacobowitz  <drow@mvista.com>
        * signals.h: New file, from gdb/defs.h.


-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


             reply	other threads:[~2002-03-29 19:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-29 11:10 Daniel Jacobowitz [this message]
2002-03-29 11:32 ` Andreas Jaeger
2002-03-29 11:38   ` Daniel Jacobowitz
2002-04-03 18:59     ` Andrew Cagney
2002-03-30 21:42 ` Eli Zaretskii
2002-03-30 21:48   ` Daniel Jacobowitz
2002-04-03 18:59     ` Andrew Cagney

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=20020329141059.B12204@nevyn.them.org \
    --to=drow@mvista.com \
    --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