This is the mail archive of the 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: coffread.c extension for DLLs without debugging symbols

On Sun, Jan 05, 2003 at 12:18:26PM -0500, Christopher Faylor wrote:
> On Sun, Jan 05, 2003 at 03:44:44PM +0100, Mark Kettenis wrote:
> >Christopher Faylor <> writes:
> >
> >>>>2) I wonder if this code should be ifdef'ed somehow for Windows since
> >>>>it will add extra code for no gain on every COFF platform.  Of course,
> >>>>how many of those are there out there?  Maybe this isn't a huge issue
> >>>>after all.
> >>>
> >>>I wondered about that myself.  However, wouldn't that suggest putting
> >>>the bulk of the code somewhere like win32-nat.c?
> >>
> >> That would be fine with me (especially since I can approve that part of
> >> gdb).  So, you'd need some kind of hooks in coffread.c to handle this.
> >> I guess we should wait for the coffread maintainer to offer an opinion
> >> before you go to this effort, though.
> >
> >Well, I assume this code would be usefull when cross-debugging too.
> >If so, a *-nat.c file would be the wrong place to add it.  You could
> >create a win32-tdep.c file though.
> Cross debugging to a windows box?  Does anyone actually do that?  I know
> it is theoretically possible with, *cough* rda *cough* but I wasn't aware
> of anyone actually doing this.
> Regardless, win32-tdep.c would be a more logically correct place to put
> it.

In any case, it's nicer to have it in the tdep file; it's a step
towards letting people who make large mechanical changes verify that it
still compiles.

Daniel Jacobowitz
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]