Re: [cdt-dev] Problem with debugging some running processes

[Heiko Jansen <jansen@xxxxxxxxxx>]

Hi again.

Am Mittwoch, 17. August 2005 20:10 schrieb "Mikhail Khodjaiants" 
<mikhailk@xxxxxxx> [Re: [cdt-dev] Problem with debugging some running processes]:

> The gdb trace may be helpful. For instructions on how to get it see CDT 
> Debugger FAQ #5.

No problem. There it is:

-- snip --

jansen@tron:/var/software/eclipse> /opt/eclipse/eclipse -debug "file:/var/software/eclipse/.options"
Start VM: /usr/bin/java
-Xms40m
-Xmx256m
-jar /opt/eclipse/startup.jar
-os linux
-ws gtk
-arch x86
-launcher /opt/eclipse/eclipse
-name Eclipse
-showsplash 600
-exitdata 2490003
-debug file:/var/software/eclipse/.options
-vm /usr/bin/java
-vmargs
-Xms40m
-Xmx256m
-jar /opt/eclipse/startup.jar
Install location:
    file:/opt/eclipse/
Configuration file:
    file:/opt/eclipse/configuration/config.ini loaded
Configuration location:
    file:/opt/eclipse/configuration/
Framework located:
    file:/opt/eclipse/plugins/org.eclipse.osgi_3.1.0.jar
Framework classpath:
    file:/opt/eclipse/plugins/org.eclipse.osgi_3.1.0.jar
Splash location:
    /opt/eclipse/plugins/org.eclipse.platform_3.1.0/splash.bmp
runCommand:
    </opt/eclipse/eclipse><-name><Eclipse><-showsplash><600></opt/eclipse/plugins/org.eclipse.platform_3.1.0/splash.bmp>
Debug options:
    file:/var/software/eclipse/.options loaded
Time to load bundles: 37
Starting application: 4658
[1.124.347.875.064] gdb --cd=/source/ips5Auto --command=.gdbinit --quiet -nw -i mi /source/ips5Auto/\
src/ipsGateways/ipsGatewayService/.libs/ipsGatewayServiceMain
[1.124.347.875.146] 1-gdb-set confirm off
[1.124.347.875.149] 1^done
[1.124.347.875.156] 2-gdb-set width 0
[1.124.347.875.157] (gdb)
[1.124.347.875.158] 2^done
[1.124.347.875.159] 3-gdb-set height 0
[1.124.347.875.160] (gdb)
[1.124.347.875.161] 3^done
[1.124.347.875.163] 4-interpreter-exec console echo
[1.124.347.875.164] (gdb)
[1.124.347.875.165] 4^done
[1.124.347.875.168] 5-gdb-show prompt
[1.124.347.875.169] (gdb)
[1.124.347.875.170] 5^done,value="(gdb) "
[1.124.347.875.175] 6 attach 7582
[1.124.347.875.184] (gdb)
[1.124.347.875.185] &"attach 7582\n"
[1.124.347.877.600] ~"[Thread debugging using libthread_db enabled]\n"
[1.124.347.877.602] ~"[New Thread 1108691456 (LWP 7582)]\n"
[1.124.347.877.604] ~"[New Thread 1271651248 (LWP 7658)]\n"
[1.124.347.877.613] ~"[New Thread 1269550000 (LWP 7657)]\n"
[1.124.347.877.614] ~"[New Thread 1267448752 (LWP 7656)]\n"
[1.124.347.877.620] ~"[New Thread 1265347504 (LWP 7655)]\n"
[1.124.347.877.622] ~"[New Thread 1263246256 (LWP 7654)]\n"
[1.124.347.877.623] ~"[New Thread 1261145008 (LWP 7653)]\n"
[1.124.347.877.625] ~"[New Thread 1259043760 (LWP 7652)]\n"
[1.124.347.877.627] ~"[New Thread 1256942512 (LWP 7651)]\n"
[1.124.347.877.631] ~"[New Thread 1254841264 (LWP 7650)]\n"
[1.124.347.877.632] ~"[New Thread 1252740016 (LWP 7649)]\n"
[1.124.347.877.633] ~"[New Thread 1250638768 (LWP 7648)]\n"
[1.124.347.877.635] ~"[New Thread 1248537520 (LWP 7647)]\n"
[1.124.347.877.637] ~"[New Thread 1246436272 (LWP 7646)]\n"
[1.124.347.877.648] ~"[New Thread 1244335024 (LWP 7645)]\n"
[1.124.347.877.649] ~"[New Thread 1242233776 (LWP 7644)]\n"
[1.124.347.877.650] ~"[New Thread 1240132528 (LWP 7643)]\n"
[1.124.347.877.651] ~"[New Thread 1238031280 (LWP 7642)]\n"
[1.124.347.877.651] ~"[New Thread 1235930032 (LWP 7641)]\n"
[1.124.347.877.652] ~"[New Thread 1233828784 (LWP 7640)]\n"
[1.124.347.877.653] ~"[New Thread 1231727536 (LWP 7639)]\n"
[1.124.347.877.654] ~"[New Thread 1229626288 (LWP 7638)]\n"
[1.124.347.877.655] ~"[New Thread 1227525040 (LWP 7637)]\n"
[1.124.347.877.656] ~"[New Thread 1225423792 (LWP 7636)]\n"
[1.124.347.877.657] ~"[New Thread 1223322544 (LWP 7635)]\n"
[1.124.347.877.657] ~"[New Thread 1221221296 (LWP 7634)]\n"
[1.124.347.877.658] ~"[New Thread 1219120048 (LWP 7633)]\n"
[1.124.347.877.659] ~"[New Thread 1217018800 (LWP 7632)]\n"

-- snip --

At this point the output stops. Some 5 seconds later Eclipse/CDT pops up a window
stating that a timeout occurred.

If I reproduce the steps in a shell I get exactly the same output except that 
after command 6 all 77 threads which are configured to run are shown and afterwards
gdb prints
-- snip --
6^done,thread-id="0",frame={addr="0xffffe410",func="??",args=[]}
(gdb)
-- / snip --

Could it be a simple timing problem with CDT being a little to impatient?
When I tried it again in Eclipse it got exactly as far as shown above: only up to thread 28.

And just to mention that: there is no ".gdbinit".

Thanks for your effort!
Heiko
--
Heiko Jansen
Cologne, Germany