Hi Spencer,
Thank's, I'm using latest master, I tried to implement patch on latest
but it's did not work.
When it crash I got this :
/Debug: 2610 2147049 gdb_server.c:2048 gdb_input_inner(): received
packet: 'Hg0'
Debug: 2611 2147049 gdb_server.c:2048 gdb_input_inner(): received
packet: 'g'/
So I searched what openOCD do when he received 'g' and found this :
/
case 'g':
retval = gdb_get_registers_packet(connection,
packet, packet_size);/
That's strange because when I hit '/info registers/' I can resume but
if I do '/info threads/' gdb crash.
So I don't think it come from /gdb_get_registers_packet()/ function
Someone know how to have a very verbose mode in gdb or openocd, (I
already use -d3 in openocd and I have nothing verbose for gdb)
I have tried to launch gdb into gdb but I haven't found nothing particular :
/
#2 0x000000000062e366 in dump_core () at utils.c:688
#3 0x00000000006307ab in internal_vproblem (ap=<optimized out>,
fmt=<optimized out>, line=<optimized out>, file=<optimized out>,
problem=0xbe6d20) at utils.c:846
#4 internal_vproblem (problem=0xbe6d20, file=<optimized out>,
line=<optimized out>, fmt=<optimized out>, ap=<optimized out>) at
utils.c:747
#5 0x00000000006308d9 in internal_verror (file=<optimized out>,
line=<optimized out>, fmt=<optimized out>, ap=ap@entry=0x7fffffffdbb8)
at utils.c:871
#6 0x0000000000630972 in internal_error (file=file@entry=0x867307
"thread.c", line=line@entry=613, string=<optimized out>) at utils.c:881
#7 0x000000000046dabd in is_thread_state (state=<optimized out>,
ptid=...) at thread.c:613
#8 0x00000000005731ce in is_exited (ptid=...) at thread.c:627
#9 0x00000000005739a2 in switch_to_thread (ptid=...) at thread.c:996
#10 0x000000000056a94a in prepare_to_proceed (step=0) at infrun.c:2067
#11 proceed (addr=addr@entry=18446744073709551615,
siggnal=siggnal@entry=GDB_SIGNAL_DEFAULT, step=step@entry=0) at
infrun.c:2181
#12 0x000000000055eba2 in continue_1 (all_threads=all_threads@entry=0)
at infcmd.c:736/
It say gdb crash executing /is_thread_state()/ function but nothing more
(stuff like variable that gdb dislike)
Best regards
Vivien
On 14/03/2013 11:56, Spencer Oliver wrote:
> On 14 March 2013 10:17, Vivien Giraud <vgir...@neotion.com> wrote:
>> Hi everyone,
>> I'm still working on implementing new CPU to RTOS.
>> ARM7TDMI and ARM926-ejs are nearly ok but I've got the same error as here.
>> After I do a "info threads" gdb crash with :
>>
>> thread.c:613: internal-error: is_thread_state: Assertion `tp' failed.
>>
>> A problem internal to GDB has been detected,
>> further debugging may prove unreliable.
>>
>>
>> Without RTOS or if I don't ask "info threads" there is no problem.
>>
>> So did someone made any improvements ?
>>
>> I saw this patch (http://sourceware.org/bugzilla/show_bug.cgi?id=12228) but
>> it's not possible to use it, fail to compile.
>>
> gdb does throw some strange errors when something fails.
>
> The last time i saw something was one i fixed the extended-remote bug
> - see
> http://openocd.zylin.com/gitweb?p=openocd.git;a=commitdiff;h=98a41bca6ed5711c972fdd75167ffc031377a456
>
> are you using latest master, if so it may be worth doing a git bisect
> around this commit 3d62c3df6ddb09f1485c25d665e248856989d180
>
> Spen
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel