Sebastien Bourdeauducq wrote:
You seem to have compiled gdb for x86. Compile it for LM32 (use
"lm32-rtems4.11" as target string) and it should work a lot better.
Okay, recompiled it from scratch and had it running with the 'airs'
patch until it froze.
gdb didn't do anything at hat point so I trapped it with ^C. But that
of course doesn't give me any usable backtrace.
===============================
[...]
^Cremote_interrupt called
remote_stop called
Packet received: T0520:408d03d8;1c:00000000;
Program received signal SIGTRAP, Trace/breakpoint trap.
0x408d03d8 in _POSIX_Barrier_Information ()
(gdb) bt
#0 0x408d03d8 in _POSIX_Barrier_Information ()
Sending packet: $m408d03d0,4#c4...Ack
Packet received: 00000003
(gdb)
===============================
A second try gave me that:
===============================
$ ~/Development/milkymist/gdb/gdb-7.2/gdb/gdb -x gdb.script
flickernoise
GNU gdb (GDB) 7.2
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show
copying"
and "show warranty" for details.
This GDB was configured as "--host=i686-pc-linux-gnu
--target=lm32-rtems4.11".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from
/home/x/Development/milkymist/milkymist/flickernoise.git/src/bin/flickernoise...done.
_CPU_Thread_Idle_body (ignored=0) at
../../../../../../../../../../../milkymist/rtems-milkymist.git/c/src/../../cpukit/score/cpu/lm32/cpu.c:172
172 asm volatile("and r0, r0, r0");
(gdb) cont
Continuing.
help
^C
Program received signal SIGTRAP, Trace/breakpoint trap.
0x40103378 in _System_state_Set (the_source=<value optimized out>,
is_internal=<value optimized out>,
the_error=<value optimized out>) at
../../cpukit/../../../milkymist/lib/include/rtems/score/sysstate.inl:37
37 _System_state_Current = state;
(gdb)
===============================
If I connect before boot, I'll get a malformed error.
If I connect after boot (as in the above two cases) flickernoise stops
until I tell it to continue (which looks okay).
Not sure if this helps much but let me know if I can run this any other
way to get you more meaningful info.
--
hadez
_______________________________________________
http://lists.milkymist.org/listinfo.cgi/devel-milkymist.org
IRC: #milkymist@Freenode
Twitter: www.twitter.com/milkymistvj
Ideas? http://milkymist.uservoice.com
