This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: [RFC] ARI fixes: Remove NAT_FILE for solaris



> -----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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]