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



>>Of course, a simpler and less intrusive fix would be to simply
>>define PREPARE_TO_PROCEED as generic_prepare_to_proceed, and >>remove lin_lwp_prepare_to_proceed.


Yes (well using set_gdbarch_prepare_to_proceed() :-). Hmm, things to do for someone --- add a linux-tdep.c file?

I've got a linux-nat already in my local tree, might as well do a
linux-tdep... but then I'd need to hook this in to all the osabi stuff,
and I'd rather not add it as GNU/Linux-specific only to make it global
after we branch.

Are you saying we should do the less invasive fix as above?  It won't
work unless I move the definition to the tm headers, since this affects
cross targets too.  I'd rather see the default changed as I proposed,
if you're comfortable with it.  Then after the branch we can look at
the other platforms which have their own custom version.

[I'm never quite clear what you mean when you answer a thread with "yes"
 :)]
I agree with michael.

I'm extreamly nervous about changing the current prepare-to-proceed behavour across all targets when the immediate problem is for just GNU/Linux. All this when we're about to branch and so should be avoiding significant change.

However, once the branch is cut, I think we should consider simply ripping out all the old code and just using the generic version.

In the mean time, for GNU/Linux, isn't it be possible to set it in the *-linux-tdep.c files? If that fails, then I guess an (ULGH and on the branch) tm*.h macro.

Andrew



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