Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Kris Warkentin" <kewarken@qnx.com>
To: "Eli Zaretskii" <eliz@is.elta.co.il>
Cc: <gdb-patches@sources.redhat.com>
Subject: Re: patch to add QNX NTO i386 support
Date: Tue, 04 Feb 2003 20:12:00 -0000	[thread overview]
Message-ID: <001601c2cc8a$0da1b5d0$2a00a8c0@dash> (raw)
In-Reply-To: <7263-Tue04Feb2003215610+0200-eliz@is.elta.co.il>

[-- Attachment #1: Type: text/plain, Size: 713 bytes --]

> > Okay, here's the patch.
>
> Thanks.
>
> However, I don't understand why did you include some of the files in
> fnchange.lst: AFAICS they don't create any conflicts.  For example:
>
> > + @V@/gdb/config/tm-qnxnto.h @V@/gdb/config/tm-qnx.h
>
> There's no other file in the gdb/config/ directory whose name will
> clash with tm-qnxnto.h after truncation to 8+3 limits.

That would be a lack of understanding on my part.  I assumed we needed to
give aliases for any filename longer than 8+3.  You're saying we just need
to be conscious of the autoconversion dos stuff.  In that case, probably the
only ones I'd need to look at would be the remote-qnx* and the tm-i386nto.h.
Revised patch attached.

cheers,

Kris

[-- Attachment #2: fnchange.diff --]
[-- Type: application/octet-stream, Size: 1042 bytes --]

*** src.orig/gdb/config/djgpp/fnchange.lst	Fri Jan 31 15:43:54 2003
--- src/gdb/config/djgpp/fnchange.lst	Tue Feb  4 08:46:56 2003
***************
*** 90,95 ****
--- 91,97 ----
  @V@/gdb/config/i386/nm-i386v4.h @V@/gdb/config/i386/nm-v4.h
  @V@/gdb/config/i386/nm-i386v42mp.h @V@/gdb/config/i386/nm-v42mp.h
  @V@/gdb/config/i386/tm-i386mk.h @V@/gdb/config/i386/tm-mk.h
+ @V@/gdb/config/i386/tm-i386nto.h @V@/gdb/config/i386/tm-nto.h
  @V@/gdb/config/i386/tm-i386sol2.h @V@/gdb/config/i386/tm-sol2.h
  @V@/gdb/config/i386/tm-i386v42mp.h @V@/gdb/config/i386/tm-v42mp.h
  @V@/gdb/config/i386/xm-i386mach.h @V@/gdb/config/i386/xm-mach.h
***************
*** 174,179 ****
--- 177,184 ----
  @V@/gdb/remote-est.c @V@/gdb/rmt-est.c
  @V@/gdb/remote-mips.c @V@/gdb/emt-mips.c
  @V@/gdb/remote-mm.c @V@/gdb/emt-mm.c
+ @V@/gdb/remote-nto.c @V@/gdb/rmt-nto.c
+ @V@/gdb/remote-nto-i386.c @V@/gdb/rmt-n386.c
  @V@/gdb/remote-nrom.c @V@/gdb/rmt-nrom.c
  @V@/gdb/remote-rdi.c @V@/gdb/rmt-rdi.c
  @V@/gdb/remote-rdp.c @V@/gdb/rmt-rdp.c

  reply	other threads:[~2003-02-04 20:12 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-03 20:19 Kris Warkentin
2003-02-04  7:23 ` Eli Zaretskii
2003-02-04 13:33   ` Kris Warkentin
2003-02-04 13:53     ` Kris Warkentin
2003-02-04 19:59       ` Eli Zaretskii
2003-02-04 20:12         ` Kris Warkentin [this message]
2003-02-05  5:50           ` Eli Zaretskii
2003-02-04 22:02 ` Andrew Cagney
2003-02-05  1:29   ` Kris Warkentin
2003-02-05  2:40     ` Andrew Cagney
2003-02-05  2:59       ` Andrew Cagney
2003-02-05 12:31         ` Kris Warkentin
2003-02-05  2:55     ` Andrew Cagney
2003-02-05 17:15   ` Kris Warkentin
2003-02-05 18:46     ` Andrew Cagney
2003-02-07  1:48   ` Kris Warkentin
2003-02-07 19:22     ` Mark Kettenis
2003-02-07 20:08       ` Kris Warkentin
2003-02-07 21:59         ` Andrew Cagney
2003-02-11 18:11           ` Kris Warkentin
2003-02-11 18:41             ` patch to add HAVE_CONTINUABLE_BREAKPOINT to target_ops Kris Warkentin
2003-02-12 22:18       ` patch to add QNX NTO i386 support Kris Warkentin
2003-02-12 22:44         ` Daniel Jacobowitz
2003-02-13  0:52           ` Kris Warkentin
2003-02-13 22:21         ` Mark Kettenis
2003-02-13 22:29           ` Kris Warkentin
2003-02-13 22:53             ` Mark Kettenis
2003-02-13 23:55               ` Kris Warkentin
2003-02-14  0:01                 ` Kris Warkentin
2003-02-13 21:56       ` Kris Warkentin
2003-02-13 22:08         ` Daniel Jacobowitz
2003-02-13 22:25           ` Kris Warkentin
2003-02-13 22:29             ` Daniel Jacobowitz
2003-02-13 23:48               ` Kris Warkentin
2003-02-14  0:03                 ` Daniel Jacobowitz
2003-02-14  0:09                   ` Kris Warkentin
2003-02-14  0:13                     ` Daniel Jacobowitz
2003-02-14  0:35                       ` Kris Warkentin
2003-02-17 14:58                         ` Andrew Cagney
2003-02-17 15:44                           ` Daniel Jacobowitz
2003-02-17 16:45                             ` Andrew Cagney
2003-02-17 18:54                               ` Kris Warkentin
2003-02-18 21:26                                 ` Andrew Cagney
2003-02-18 22:30                                   ` Kris Warkentin
2003-02-20  0:42                                     ` Andrew Cagney
2003-02-27 19:02                             ` Kris Warkentin
2003-02-27 19:56                               ` Andrew Cagney
2003-02-27 20:02                               ` Daniel Jacobowitz
2003-02-27 20:10                                 ` Andrew Cagney
2003-02-27 20:11                                 ` Kris Warkentin
2003-02-27 20:23                                   ` Andrew Cagney
2003-02-27 20:28                                     ` Kris Warkentin
2003-02-05 20:48 ` Mark Kettenis
2003-02-05 21:23   ` Kris Warkentin
2003-02-05 21:43     ` Kris Warkentin
2003-02-05 22:24       ` Mark Kettenis
2003-02-06 15:13         ` Kris Warkentin
2003-02-06 18:19           ` Andrew Cagney
2003-02-05 22:48     ` Mark Kettenis
2003-02-06 15:08       ` Kris Warkentin

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='001601c2cc8a$0da1b5d0$2a00a8c0@dash' \
    --to=kewarken@qnx.com \
    --cc=eliz@is.elta.co.il \
    --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