GDB for target mips2_fp_le

GDB for target mips2_fp_le

[Geert Vancompernolle]

Hi,

I just asked the following questions in the Insight forum (GUI for the 
GDB debugger), but they advised me to post the question in the GDB forum:

1. When running "./config.sub mips" before building Red Hat Insight, I 
only get the target "mips-unknown-elf".
   Is there a possibility to compile for mips2_fp_le? Can 
mips-unknown-elf be used for mips2_fp_le?

2. Is it possible to build for a Windows host and a Linux target?
   I would like to know if I can run Insight on a Win32 platform and 
using it to debug an embedded Linux system.

Thanks in advance for any kind of advice.

Best rgds,

--Geert

Re: GDB for target mips2_fp_le

[Daniel Jacobowitz]

On Wed, May 07, 2008 at 08:14:11PM +0200, Geert Vancompernolle wrote:
> Hi,
>
> I just asked the following questions in the Insight forum (GUI for the  
> GDB debugger), but they advised me to post the question in the GDB forum:
>
> 1. When running "./config.sub mips" before building Red Hat Insight, I  
> only get the target "mips-unknown-elf".
>   Is there a possibility to compile for mips2_fp_le? Can mips-unknown-elf 
> be used for mips2_fp_le?

It sounds like you want "mips-linux" since mips2_fp_le is what
MontaVista calls one of their Linux targeted toolchains.

> 2. Is it possible to build for a Windows host and a Linux target?
>   I would like to know if I can run Insight on a Win32 platform and using 
> it to debug an embedded Linux system.

Yes for GDB, but I don't know about Insight.  For that you may require
Cygwin.

-- 
Daniel Jacobowitz
CodeSourcery

Re: GDB for target mips2_fp_le

[Geert Vancompernolle]

On Wed, May 7, 2008 at 8:18 PM, Daniel Jacobowitz <drow@false.org> wrote:
> On Wed, May 07, 2008 at 08:14:11PM +0200, Geert Vancompernolle wrote:
>> Hi,
>>
>> I just asked the following questions in the Insight forum (GUI for the
>> GDB debugger), but they advised me to post the question in the GDB forum:
>>
>> 1. When running "./config.sub mips" before building Red Hat Insight, I
>> only get the target "mips-unknown-elf".
>>   Is there a possibility to compile for mips2_fp_le? Can mips-unknown-elf
>> be used for mips2_fp_le?
>
> It sounds like you want "mips-linux" since mips2_fp_le is what
> MontaVista calls one of their Linux targeted toolchains.
>

Ok, so I assume I can take the "risk" and use "mips-unknown-elf" to
try to debug a target having "mips2_fp_le" then?

>> 2. Is it possible to build for a Windows host and a Linux target?
>>   I would like to know if I can run Insight on a Win32 platform and using
>> it to debug an embedded Linux system.
>
> Yes for GDB, but I don't know about Insight.  For that you may require
> Cygwin.
>
> --
> Daniel Jacobowitz
> CodeSourcery
>

Reason why I'm asking this:

I've compiled Insight for PC host and mips-unknown-elf for target.

However, when running Insight on the PC platform (not Linux) and then
trying to start debugging the mips2_fp_le target, I'm getting the
following pop-up dialogue:

Begin quote

A handler for the OS ABI "GNU/Linux" is not built into this
configuration of GDB.  Attempting to continue with the default
mips:6000 settings.

End quote

What am I missing while compiling GDB for mips, that is causing this problem?

Best rgds,

--Geert

Re: GDB for target mips2_fp_le

[Daniel Jacobowitz]

On Fri, May 09, 2008 at 07:39:27AM +0200, Geert Vancompernolle wrote:
> Ok, so I assume I can take the "risk" and use "mips-unknown-elf" to
> try to debug a target having "mips2_fp_le" then?

If you are trying to use Linux on your target then use the Linux
configuration as I suggested in my message.

-- 
Daniel Jacobowitz
CodeSourcery

Re: GDB for target mips2_fp_le

[Geert Vancompernolle]

On Fri, May 9, 2008 at 2:02 PM, Daniel Jacobowitz <drow@false.org> wrote:
> On Fri, May 09, 2008 at 07:39:27AM +0200, Geert Vancompernolle wrote:
>> Ok, so I assume I can take the "risk" and use "mips-unknown-elf" to
>> try to debug a target having "mips2_fp_le" then?
>
> If you are trying to use Linux on your target then use the Linux
> configuration as I suggested in my message.
>

Indeed, that's what I've done.

But the second question, regarding the OS ABI stuff, is my main
concern now.  Any suggestions?

Best rgds,

--Geert

Re: GDB for target mips2_fp_le

[Daniel Jacobowitz]

On Fri, May 09, 2008 at 03:18:58PM +0200, Geert Vancompernolle wrote:
> On Fri, May 9, 2008 at 2:02 PM, Daniel Jacobowitz <drow@false.org> wrote:
> > On Fri, May 09, 2008 at 07:39:27AM +0200, Geert Vancompernolle wrote:
> >> Ok, so I assume I can take the "risk" and use "mips-unknown-elf" to
> >> try to debug a target having "mips2_fp_le" then?
> >
> > If you are trying to use Linux on your target then use the Linux
> > configuration as I suggested in my message.
> >
> 
> Indeed, that's what I've done.
> 
> But the second question, regarding the OS ABI stuff, is my main
> concern now.  Any suggestions?

If you are getting that message then you are using mips-elf, not
mips-linux.

-- 
Daniel Jacobowitz
CodeSourcery

Re: GDB for target mips2_fp_le

[Geert Vancompernolle]

Daniel Jacobowitz wrote:
>
> If you are getting that message then you are using mips-elf, not
> mips-linux.
Apologize, I've misinterpret your previous answers.  I was not aware 
there was a target called "mips-linux", as you indicated.

What I find a bit confusing (but that's most probably Insight related, 
not GDB), is that "./config.sub mips" is not giving me all the possible 
options.  I only got "mips-unknown-elf" as feedback, while there are 
many more possibilities (I've even seen mipsle in the configure script).
AFAIK, "config.sub" is giving you (or should give you) all the possible 
options for a (part of a) string that you're giving as an argument.  But 
apparently that's not always true.

Hence, my confusion.  But it's clear now.

Thanks anyhow for your patience.

Best rgds,

--Geert

Re: GDB for target mips2_fp_le

[Andreas Schwab]

Geert Vancompernolle <geert.vancompernolle@gmail.com> writes:

> AFAIK, "config.sub" is giving you (or should give you) all the possible
> options for a (part of a) string that you're giving as an argument.

The purpose of config.sub is to validate and canonicalize a
configuration type.  See the comments at the start of the file.  It
never outputs more than one configuration name, underspecified parts of
the name are resolved by replacing that part with a sensible default.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."