From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Pedro Alves'" <pedro@codesourcery.com>, <gdb-patches@sourceware.org>
Subject: RE: [RFC] ARI fixes: Remove NAT_FILE for solaris
Date: Fri, 09 Apr 2010 18:44:00 -0000 [thread overview]
Message-ID: <000001cad814$9ae9a770$d0bcf650$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <201004091713.19282.pedro@codesourcery.com>
> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Pedro Alves
> Envoyé : Friday, April 09, 2010 6:13 PM
> À : gdb-patches@sourceware.org
> Cc : Pierre Muller
> Objet : Re: [RFC] ARI fixes: Remove NAT_FILE for solaris
>
> On Friday 09 April 2010 17:10:50, Pierre Muller wrote:
> > This patch simply removes i386/nm-i386sol2.h
> >
> > The only remaining code was
> > #ifdef NEW_PROC_API
> > #define CANNOT_STEP_HW_WATCHPOINTS
> > #endif
> >
> > I moved that into gdb/configure.ac.
> > The most difficult part was to get all the tools
> > (in the correct versions) to be able to regenerate
> > config.in and configure on a solaris machine.
>
> This fixes nothing. There's a reason we want to get rid
> of macros defined in nm files and used in common code. As is,
> a cross debugger hosted on solaris behaves differently from
> a cross debugger hosted on all other hosts.
I agree, but I thought that doing this step by step would be easier...
My big patches take ages to get in, so I prefer to do it bitwise!
How could we change this so that this
would only trigger if we are debugging native and not some other
target?
Could we change the macro
into a test that the current target is native solaris?
I don't know enough on gdbarch and tdep structures
to have an idea how to write such a test.
Advices welcome.
Pierre
next prev parent reply other threads:[~2010-04-09 18:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-09 16:10 Pierre Muller
2010-04-09 16:13 ` Pedro Alves
2010-04-09 18:44 ` Pierre Muller [this message]
2010-04-09 19:42 ` Pedro Alves
2010-04-22 23:35 ` [RFC-v2] " Pierre Muller
2010-04-23 1:13 ` Pedro Alves
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='000001cad814$9ae9a770$d0bcf650$@muller@ics-cnrs.unistra.fr' \
--to=pierre.muller@ics-cnrs.unistra.fr \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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