This is the mail archive of the gdb-patches@sources.redhat.com 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: [rfa] gdbserver signal handling


On Thu, Feb 28, 2002 at 10:01:00AM -0500, Andrew Cagney wrote:
> >2002-02-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/signals.c: New file.
> >	* gdbserver/server.h: Add prototypes.
> >	* gdbserver/Makefile.in: Add signals.o.
> >
> >
> 
> Er, why did you create src/gdb/signals.c?

The reason to create src/gdb/signals.c has nothing to do with
gdbserver; it has to do with:
  - the cleanup I never got to of removing <signal.h> from target.c,
  since <signal.h> is a host header but used for target information.

  - the eventual moving of signals.c to be in NATDEPFILES.

I don't want to move it to gdbserver, because I've finally reached no
code sharing.  And because of something you said once, which is now
true:
> I think, in terms of better splitting up gdbserver and gdb it is pretty
> much a requirement.  I can but dream of the day when GDBSERVER stops
> including defs.h :-)


That's why I wanted to do it the above way.

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


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