[ECOS] Re: A build and a debug question

[Gary D. Thomas]

On Tue, 2003-03-25 at 07:29, Westwood, Geoff wrote:
> Hello Both
> 
> Thanks for taking the time to help with my gdb problem
> 

Sorry, but private help is only available on contract.  Email sent
directly to me in the future that is not copied to the list will
be quietly ignored. I am copying this to the list so that everyone 
can benefit from this free service.If you want private support, 
contact me.

> I am at work now so I had chance to test this again
> 
> I am using the Viper PowerPC 855T board, Building using  Cygwin on Win NT
> and the Gui config tool
> 

What Viper 855T? - the Viper from Analogue & Micro is an 860T
(not that it makes much difference at this point)

> I started again this morning by clearing my build directory and rebuilding
> the library for the Viper default build.
> I then built the Viper hello.c test. This builds OK, and downloads using
> gdb, and runs fine cycles leds and outputs text to the gdb console
> 
> I then deleted the build dir contents for tidiness and just changed the
> default package to "new_net" package and built again. This built ok , note I
> did get a window asking about resolving conflicts, I just clicked on
> continue in this window. This builds and I can compile and link the hello.c
> program.
> however when I  use gdb ( powerpc-eabi-gdb -nw hello.exe) and after typing
> target remote 10.20.111.111:9000 I get the error
> 
> (gdb) target remote 10.20.111.111:9000
> Remote debugging using 10.20.111.111:9000
> gdb-internal-error: longest_local_hex_string_custom: insufficient space to
> store result
> 

What happens if you try to connect via the serial port?
Have you tried turning on GDB debugging (set remotedebug 1)?  This will
show something of what's going on.

If it works with one configurstion and not another, what's the 
difference between them?  In this case, the executable will be somewhat
larger, but much less than the available memory size.

> I am using the ecos snapshot   "ecos-v2-full-beta-snap-2003-03-10.tar.bz2",
> I unzipped this onto a network drive and pointed the config tool at this
> repository.
> 
> I am sure this fault is triggered just by me selecting "new_net" and it is
> 100% repeatable for me. I did wonder if I should be using "net" instead of
> "new_net"
> I tried to build with "net"  but eCos wouldn't build, so I concluded I was
> correct first time in using "new_net"

>From the snapshot you are using, both network stacks built fine.  What
problem did you encounter?

> 
> Not sure what else I can tell you regarding my setup ? Thanks for any
> thoughts you might have on this problem
> 
> 	Regards Geoff Westwood
> 
-- 
.--------------------------------------------------------.
|       Mind: Embedded Linux and eCos Development        |
|--------------------------------------------------------|
| Gary Thomas              email:  gary.thomas@mind.be   |
| Mind ( http://mind.be )  tel:    +1 (970) 229-1963     |
| gpg: http://www.chez-thomas.org/gary/gpg_key.asc       |
'--------------------------------------------------------'


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss