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: [PATCH v2 7/9] compile: New 'compile print'


> On Apr 6, 2015, at 1:52 PM, Jan Kratochvil <jan.kratochvil@redhat.com> wrote:
> 
> On Mon, 06 Apr 2015 19:49:28 +0200, Paul_Koning@dell.com wrote:
>> where does it run?  Presumably on the target.
> 
> Yes.
> 
>> Does it only work for native gdb?
> 
> Yes.
> 
>> Does it work with gdbserver?
> 
> Yes.
> 
>> It would be good to state the limitations and assumptions.
> 
> I am not aware of any, there may be needed some target-specific support like
> for s390 gcc -m31 but in general it should work.
> 
> I could pick some 10 years old discussion that NEWS file should not contain
> limitations, that those are just bugs for future ChangeLog entries.

I meant limitations such as “native only”.   But given that it works across the board (give or take bugs) I agree that NEWS doesn’t need to say anything further.
> 
> 
>> Also, “the compiler” begs the question: which one, i.e., how is “the
>> compiler” found?
> 
> A complicated way, for non-native targets an appropriate cross-gcc should be
> found.

Ok.  I would not expect that to be documented in NEWS, but it seems like it should be in gdb.texinfo or some similar spot.  I have a whole pile of cross-compilers in various places; I would need to understand what the algorithm looks like to be able to ensure that the correct one is found.  

	paul


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