[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[List Home]
|
Re: [cdt-dev] Couple issues with DSF
|
- From: Dmitry Smirnov <divis1969@xxxxxxxxx>
- Date: Thu, 12 Feb 2009 12:28:23 +0300
- Delivered-to: cdt-dev@eclipse.org
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=gHzPDQX1wQ/JFmLC0nUZIW3z9TAZeWxiQzJxDXiRtQk=; b=N05t6Hm8wqNo4XBqQro5UBUendqW8qieExdnnI3ldFHmZwuxsq4XNubomkpU/+GKg2 0VAJTSuZ8Je1CofZdPJlpRlPNRAlj5MeVvrIx3pjviZ4gry6WXHWlkn9QaZ9ajQHumKo bJxMjdc5/GQMirX5BRnZB4q6Of1IOAm4Ue/e8=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=YluxvUhXdK2a/hrIDn7YmsFdZGt0UBeO369LiDlI0PjzF8RCuHmnhyv6HGGIgLOdkq IHGdxEN10lY+q4trjiz99njuTBejRPh1ZOU/1XyTUg2WJTHzoYBec0q1rIGUfYZ8Aq5b YHK20x8qVa9dHws7dmJdMb0HeNJLZYX5T6OIM=
>> > Sure. You can start the debugging in MI mode: gdb -i mi
>> > Even easier, you can run an MI command outside of MI mode like this:
>> > interpreter-exec mi -stack-list-frames
(gdb) interpreter-exec mi -stack-list-frames
^done,stack=[frame={level="0",addr="0x00c1d1f2",func="tmc_init",file="qct\\servi
ces\\tmc\\tmc.c",fullname="/c/p4/views/KSW_M2000_ZQ_DEV_0331/qct/services/tmc/tm
c.c",line="11541"},frame={level="1",addr="0x00c1d4c6",func="tmc_task",file="qct\
\services\\tmc\\tmc.c",fullname="/c/p4/views/KSW_M2000_ZQ_DEV_0331/qct/services/
tmc/tmc.c",line="12350"},frame={level="2",addr="0x00eee43e",func="rex_thread_ini
t",file="qct\\services\\rexl4\\rexl4.c",fullname="/c/p4/views/KSW_M2000_ZQ_DEV_0
331/qct/services/rexl4/rexl4.c",line="174"},frame={level="3",addr="0x00f3e0c8",f
unc="__thread_stub"},frame={level="4",addr="0x00f3e0c8",func="__thread_stub"}]
> You can get those traces by launching eclipse with
> -debug ~/dsf.debug.options
>
> where dsf.debug.options contains
>
> org.eclipse.dd.mi/debug = true
> org.eclipse.cdt.dsf.gdb/debug = true
Here is the tail of the trace:
637,375 (gdb)
637,391 6-target-select remote localhost:12345
637,625 =thread-created,id="1"
637,672 *stopped,thread-id="1",frame={addr="0xffff0000",func="??",args=[]}
637,672 6^connected
637,672 (gdb)
637,735 7-break-insert -t tmc_init
637,813 8-thread-list-ids
641,032 7^done,bkpt={number="1",type="breakpoint",disp="del",enabled="y",addr="0
x00c1d1f2",func="tmc_init",file="qct\\services\\tmc\\tmc.c",line="11541",times="
0",original-location="tmc_init"}
641,032 (gdb)
641,032 9-exec-continue
641,063 &"warning: RMT ERROR : failed to get remote thread list.\n"
641,063 8^done,thread-ids={thread-id="1"},number-of-threads="1"
641,063 (gdb)
641,063 10-stack-info-depth --thread 1 11
641,063 9^running
641,063 *running,thread-id="all"
641,063 (gdb)
696,769 *stopped,reason="breakpoint-hit",disp="del",bkptno="1",thread-id="1",fra
me={addr="0x00c1d1f2",func="tmc_init",args=[],file="qct\\services\\tmc\\tmc.c",l
ine="11541"}
696,769 (gdb)
696,769 10^error,msg="mi_cmd_stack_info_depth: Usage: [MAX_DEPTH]"
696,769 (gdb)
696,925 11info threads
696,940 &"info threads\n"
696,940 &"warning: RMT ERROR : failed to get remote thread list.\n"
696,940 ~"* 1 Thread <main> tmc_init () at qct\\services\\tmc\\tmc.c:11541\n"
696,940 11^done
696,940 (gdb)