Home » Eclipse Projects » Eclipse Platform » Too much MI commands send to gdb during debugging
| Too much MI commands send to gdb during debugging [message #333035] |
Fri, 21 November 2008 06:40  |
 xingyun
Messages: 27
Registered: July 2009
Location: Bei jing |
Junior Member |
|
|
Hi all:
My steps:
1. Attach to a running process, I've unchecked "tracking variables
and signals" in "Debugger -> Advanced" tab
2. I have Registers View/Variables View open
3. Set breakpoint
4. Debug step by step
What i see:
When a breakpoint is hit, CDT sends too much MI commands to GDB
(output is below)
It's already a performance killer, and it gets even worse if i turn
on "tracking variables and signals".
I have to wait for a long time during stepping.
Can i disable sending those commands during debugging? (Only send those
command when i click on Variables View/Registers View)
Regards
Xing Yun
35^done,depth="3"
(gdb)
36-stack-list-frames 0 3
36^done,stack=[frame={level="0",addr="0x66956144",func="GetTimeDate ",file="actmain.c",line="549"},frame={level="1",addr="0x66955ab5 ",func="actmain",file="actmain.c",line="1934"},frame={level= "2",addr="0x0040101a",func="main",file="actmainmain.c",line= "53"}]
(gdb)
37info mailbox
&"info mailbox\n"
37^done,pdeinfo={line="0//: found\r",line=" MbxId Part Vproc Owner
MsgCount MbxName Flags MsgDQCount\r",line=" 68 0 1720
0 1\r",line="found\r",line=" 56 11 0
1720 0 2-11 Work 772\r",line="found\r",line=" 57
11 0 1720 0 3-11
1\r",line="found\r",line=" 58 11 0 1720 0 4-11
15\r",line="found\r",line=" 59 11 0 1720 0 5-11
0\r",line="found\r",line=" 64 11 0 1720 0 6-11
2\r",line="found\r",line=" 55 11 0 1720 0 7-11
5\r",line="found\r",line=" 65 11 0 1720 0 8-11
2\r",line="found\r",line=" 61 11 0 1720 0 10-11
0\r",line="found\r",line=" 62 11 0 1720 0 12-11
5\r",line="found\r",line=" 63 11 0 1720 0 13-11
0\r",line="found\r",line=" 60 11 0 1720 0 22-11
0\r"}
(gdb)
38-stack-list-arguments 0 0 0
38^done,stack-args=[frame={level="0",args=[name="TimeAndDate ",name="QuadTime"]}]
(gdb)
39-stack-list-locals 0
39^done,locals=[name="RetCode"]
(gdb)
40 whatis TimeAndDate
&"whatis TimeAndDate\n"
~"type = struct timtimeanddate_t *\n"
40^done
(gdb)
41 whatis QuadTime
&"whatis QuadTime\n"
~"type = short *\n"
41^done
42 whatis RetCode
(gdb)
&"whatis RetCode\n"
~"type = int\n"
42^done
(gdb)
43-thread-select 1
43^done,new-thread-id="1",frame={level="0",addr="0x7c82ed54 ",func="KiFastSystemCallRet",args=[]}
(gdb)
44-stack-info-depth
44^done,depth="8"
(gdb)
45-stack-info-depth
45^done,depth="8"
46-thread-select 20
(gdb)
46^done,new-thread-id="20",frame={level="0",func="GetTimeDate ",args=[{name="TimeAndDate",value="0x66ad9ec8"},{name="QuadTime ",value="0x66adb444"}],file="actmain.c",line="549"},line= "549",file="actmain.c"
(gdb)
47-thread-select 1
47^done,new-thread-id="1",frame={level="0",addr="0x7c82ed54 ",func="KiFastSystemCallRet",args=[]}
(gdb)
48-stack-list-frames 0 8
48^done,stack=[frame={level="0",addr="0x7c82ed54",func="KiFastSystemCallRet "},frame={level="1",addr="0x7c8213e4",func="ZwDeviceIoControlFile "},frame={level="2",addr="0x77e416f1",func="DeviceIoControl "},frame={level="3",addr="0x60202019",func="syscalldriver ",file="syscall.c",line="240"},frame={level="4",addr="0x6021a593 ",func="msgrxsegrec",file="msglib.c",line="701"},frame={level= "5",addr="0x66948c84",func="awtmain",file="awtmain.c",line= "2522"},frame={level="6",addr="0x601f607d",func="tsknewthread ",file="tskport.c",line="1182"},frame={level="7",addr= "0x77e6608b",func="GetModuleFileNameA"}]
(gdb)
49-thread-select 20
49^done,new-thread-id="20",frame={level="0",func="GetTimeDate ",args=[{name="TimeAndDate",value="0x66ad9ec8"},{name="QuadTime ",value="0x66adb444"}],file="actmain.c",line="549"},line= "549",file="actmain.c"
(gdb)
|
|
|
| Re: Too much MI commands send to gdb during debugging [message #333036 is a reply to message #333035] |
Fri, 21 November 2008 06:49  |
xingyun
Messages: 27
Registered: July 2009
Location: Bei jing |
Junior Member |
|
|
Really sorry for posting it in a incorrect group
Please neglect this one..
Regards
Xing Yun
"xing yun" <cx186000@teradata.com> wrote in message
news:gg5l58$s2g$1@build.eclipse.org...
> Hi all:
> My steps:
> 1. Attach to a running process, I've unchecked "tracking variables
> and signals" in "Debugger -> Advanced" tab
> 2. I have Registers View/Variables View open
> 3. Set breakpoint
> 4. Debug step by step
> What i see:
> When a breakpoint is hit, CDT sends too much MI commands to GDB
> (output is below)
>
> It's already a performance killer, and it gets even worse if i
> turn on "tracking variables and signals".
>
> I have to wait for a long time during stepping.
>
> Can i disable sending those commands during debugging? (Only send those
> command when i click on Variables View/Registers View)
>
> Regards
> Xing Yun
>
>
>
> 35^done,depth="3"
> (gdb)
> 36-stack-list-frames 0 3
> 36^done,stack=[frame={level="0",addr="0x66956144",func="GetTimeDate ",file="actmain.c",line="549"},frame={level="1",addr="0x66955ab5 ",func="actmain",file="actmain.c",line="1934"},frame={level= "2",addr="0x0040101a",func="main",file="actmainmain.c",line= "53"}]
> (gdb)
> 37info mailbox
> &"info mailbox\n"
> 37^done,pdeinfo={line="0//: found\r",line=" MbxId Part Vproc Owner
> MsgCount MbxName Flags MsgDQCount\r",line=" 68 0
> 1720 0 1\r",line="found\r",line=" 56 11
> 0 1720 0 2-11 Work 772\r",line="found\r",line="
> 57 11 0 1720 0 3-11 1\r",line="found\r",line=" 58
> 11 0 1720 0 4-11 15\r",line="found\r",line=" 59
> 11 0 1720 0 5-11 0\r",line="found\r",line=" 64
> 11 0 1720 0 6-11 2\r",line="found\r",line=" 55
> 11 0 1720 0 7-11 5\r",line="found\r",line=" 65
> 11 0 1720 0 8-11 2\r",line="found\r",line=" 61
> 11 0 1720 0 10-11 0\r",line="found\r",line=" 62
> 11 0 1720 0 12-11 5\r",line="found\r",line=" 63
> 11 0 1720 0 13-11 0\r",line="found\r",line=" 60
> 11 0 1720 0 22-11 0\r"}
> (gdb)
> 38-stack-list-arguments 0 0 0
> 38^done,stack-args=[frame={level="0",args=[name="TimeAndDate ",name="QuadTime"]}]
> (gdb)
> 39-stack-list-locals 0
> 39^done,locals=[name="RetCode"]
> (gdb)
> 40 whatis TimeAndDate
> &"whatis TimeAndDate\n"
> ~"type = struct timtimeanddate_t *\n"
> 40^done
> (gdb)
> 41 whatis QuadTime
> &"whatis QuadTime\n"
> ~"type = short *\n"
> 41^done
> 42 whatis RetCode
> (gdb)
> &"whatis RetCode\n"
> ~"type = int\n"
> 42^done
> (gdb)
> 43-thread-select 1
> 43^done,new-thread-id="1",frame={level="0",addr="0x7c82ed54 ",func="KiFastSystemCallRet",args=[]}
> (gdb)
> 44-stack-info-depth
> 44^done,depth="8"
> (gdb)
> 45-stack-info-depth
> 45^done,depth="8"
> 46-thread-select 20
> (gdb)
> 46^done,new-thread-id="20",frame={level="0",func="GetTimeDate ",args=[{name="TimeAndDate",value="0x66ad9ec8"},{name="QuadTime ",value="0x66adb444"}],file="actmain.c",line="549"},line= "549",file="actmain.c"
> (gdb)
> 47-thread-select 1
> 47^done,new-thread-id="1",frame={level="0",addr="0x7c82ed54 ",func="KiFastSystemCallRet",args=[]}
> (gdb)
> 48-stack-list-frames 0 8
> 48^done,stack=[frame={level="0",addr="0x7c82ed54",func="KiFastSystemCallRet "},frame={level="1",addr="0x7c8213e4",func="ZwDeviceIoControlFile "},frame={level="2",addr="0x77e416f1",func="DeviceIoControl "},frame={level="3",addr="0x60202019",func="syscalldriver ",file="syscall.c",line="240"},frame={level="4",addr="0x6021a593 ",func="msgrxsegrec",file="msglib.c",line="701"},frame={level= "5",addr="0x66948c84",func="awtmain",file="awtmain.c",line= "2522"},frame={level="6",addr="0x601f607d",func="tsknewthread ",file="tskport.c",line="1182"},frame={level="7",addr= "0x77e6608b",func="GetModuleFileNameA"}]
> (gdb)
> 49-thread-select 20
> 49^done,new-thread-id="20",frame={level="0",func="GetTimeDate ",args=[{name="TimeAndDate",value="0x66ad9ec8"},{name="QuadTime ",value="0x66adb444"}],file="actmain.c",line="549"},line= "549",file="actmain.c"
> (gdb)
>
>
>
|
|
|
Goto Forum:
Current Time: Tue Nov 12 22:22:11 GMT 2024
Powered by FUDForum. Page generated in 0.03241 seconds |
] 
Search
Help
Register
Login
Home
