This is the mail archive of the
ecos-devel@sourceware.org
mailing list for the eCos project.
Re: eCos GNU tools 4.6.2-20120125 ready for testing [Was Re: Gnutools: consideration for upgrade to GCC 4.6]
- From: Alex Schuilenburg <alexs at ecoscentric dot com>
- To: Sergei Gavrikov <sergei dot gavrikov at gmail dot com>
- Cc: Ilija Kocho <ilijak at siva dot com dot mk>, eCos developers <ecos-devel at ecos dot sourceware dot org>
- Date: Sun, 04 Mar 2012 23:08:09 +0000
- Subject: Re: eCos GNU tools 4.6.2-20120125 ready for testing [Was Re: Gnutools: consideration for upgrade to GCC 4.6]
- References: <4F106345.4080902@siva.com.mk> <4F11574D.9070002@dallaway.org.uk> <4F11AC54.7000902@siva.com.mk> <4F1CB41C.90900@jifvik.org> <4F1DA9A0.5070702@siva.com.mk> <4F1FF5AD.4010901@ecoscentric.com> <4F39887A.5050905@siva.com.mk> <4F50F700.5080902@ecoscentric.com> <4F521D6A.4010500@siva.com.mk> <4F52B2C8.4010809@schuilenburg.org> <alpine.DEB.2.00.1203042011030.22265@vostro>
On 04/03/2012 17:49, Sergei Gavrikov wrote:
> [...]
>
> Hi Alex
>
> I just wonder, is there
>
> set cyg_test_is_simulator=0
>
> line in your gdbinit file?
We don't use gdbint. Our testfarm uses a mixture of perl and expect to
drive the tests, mainly so we can add additional automatic diagnostic
code when something goes wrong.
Anyway, as I mentioned, the tests do not even hit the initial
cyg_test_init breakpoint so they do not get to that stage.
> [...]
>
>
> GDB 7.3.1
>
> (gdb) set cyg_test_is_simulator=0
> No symbol "cyg_test_is_simulator" in current context.
>
> IMHO, this claim is okay, adn GDB 7.3.1 does not process the next lines in
> gdbinit.
It is OK. Not as bad as some versions of gdb which interpreted no
symbol as NULL and so would write 0 to NULL. They always gave
interesting results, but the gdb code segment below worked around this:
if &cyg_test_is_simulator!=0
set cyg_test_is_simulator=0
end
FWIW, using gdbinit or user-defined command files does not always work
for this exact reason - gdb will stop on the first error. This is why
we have our own scripts, although you could also use the gui configtool
which uses a simplistic but reasonable approach.
However, dropping "set cyg_test_is_simulator=0" for running tests on
hardware is a good idea since it will be zero as it is in .bss. You
could try the code segment above as another alternative.
-- Alex