Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Kris Warkentin" <kewarken@qnx.com>
To: "Andrew Cagney" <ac131313@redhat.com>
Cc: <gdb-patches@sources.redhat.com>
Subject: Re: patch to add QNX NTO i386 support
Date: Fri, 07 Feb 2003 01:48:00 -0000	[thread overview]
Message-ID: <008f01c2ce4b$427295f0$2a00a8c0@dash> (raw)
In-Reply-To: <3E40387D.50001@redhat.com>

> >     * config/i386/nm-nto.h: New file
>
> The file nm-nto.h should not be needed.  Instead define it's only macro
>   local to remote-nto.c.  (Disclaimer, you're breaking new ground with
> this one.  Some existing targets  don't have xm-*.h files, but I think
> you're first with the no-*.h file).
>
> >     * config/i386/nto.mh: New file
>
> Yes, you need this, you've a native support.

When I got rid of nm-nto.h and took out 'NAT_FILE=nm-nto.h' from nto.mh, all
of a sudden I wasn't building a native compiler anymore.  Looks like
configure uses the presence of a native file to determine whether to build a
self hosted debugger or not.  If I just 'touch nm-nto.h' and reconfigure, I
build a native gdb.  Any suggestions?  I was thinking that I could perhaps
point to one of my other headers and then share some remote and native
definitions.

As long as I'm asking questions, below is what I've reduced our tm-i386nto.h
file to.  Is it absolutely verboten to have this file?  There are a few
handy definitions there like EXTRA_GDBINIT and so on that we like to define
per target.  Also, I couldn't see how to get rid of the solib stuff.  Is
there some place else I can put these definitions?

cheers,

Kris

#ifndef TM_I386QNX_H
#define TM_I386QNX_H 1

/* Pick up most of what we need from the generic i386 target include file.
*/

#include "i386/tm-i386.h"
#include "tm-qnxnto.h"

#define __QNXTARGET__
#define QNX_TARGET_CPUTYPE CPUTYPE_X86

/* After a watchpoint trap, the PC points to the instruction after
   the one that caused the trap.  Therefore we don't need to step over it.
   But we do need to reset the status register to avoid another trap.  */
#define HAVE_CONTINUABLE_WATCHPOINT

/* default processor for search path for libs */
#define SOLIB_PROCESSOR "x86"

/* Use .ntox86-gdbinit */
#define EXTRA_GDBINIT_FILENAME ".ntox86-gdbinit"

#define HANDLE_SVR4_EXEC_EMULATORS 1
#include "solib.h" /* shared lib support */

#endif /* ifndef TM_I386QNX_H */


  parent reply	other threads:[~2003-02-07  1:48 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
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 [this message]
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='008f01c2ce4b$427295f0$2a00a8c0@dash' \
    --to=kewarken@qnx.com \
    --cc=ac131313@redhat.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