← Back to team overview

kicad-developers team mailing list archive

Infinite look taking 100% cpu when building debug mode.

 

Hello all:

I've build kicad several times and I've noticed that if I do a debug 
build -DCMAKE_BUILD_TYPE=Debug, then eeschema or pcbnew works but uses lots 
of cpu time. I got some backtraces, build for svn r983

(gdb) bt
#0 0x00002ab213fd427a in pthread_mutex_lock () from /lib/libpthread.so.0
#1 0x00002ab2160ac80f in IA__g_main_context_prepare (context=0x9fc100, 
priority=0x7fff994441c4) at /tmp/buildd/glib2.0-2.16.3/glib/gmain.c:2258
#2 0x00002ab2160ad028 in g_main_context_iterate (context=0x9fc100, block=1, 
dispatch=1, self=<value optimized out>)
at /tmp/buildd/glib2.0-2.16.3/glib/gmain.c:2622
#3 0x00002ab2160ad657 in IA__g_main_loop_run (loop=0xd0ebd0) 
at /tmp/buildd/glib2.0-2.16.3/glib/gmain.c:2850
#4 0x00002ab214a90b63 in IA__gtk_main () 
at /build/buildd/gtk+2.0-2.12.9/gtk/gtkmain.c:1163
#5 0x00002ab211d5b4e1 in wxEventLoop::Run () 
from /usr/lib/libwx_gtk2u_core-2.6.so.0
#6 0x00002ab211de2c2b in wxAppBase::MainLoop () 
from /usr/lib/libwx_gtk2u_core-2.6.so.0
#7 0x0000000000659723 in WinEDA_App::OnRun (this=0x9fbf50) 
at /home/rasasi/debs/kicad/pkg/kicad/common/edaappl.cpp:674
#8 0x00002ab21190aeec in wxEntry () from /usr/lib/libwx_baseu-2.6.so.0
#9 0x00000000005a5f0e in main (argc=2, argv=0x7fff99444448) 
at /home/rasasi/debs/kicad/pkg/kicad/pcbnew/pcbnew.cpp:29

Another one a little later:

(gdb) bt
#0 0x00002ab2142a59a7 in ioctl () from /lib/libc.so.6
#1 0x00002ab2134599f4 in _XEventsQueued () from /usr/lib/libX11.so.6
#2 0x00002ab2134462dd in XPending () from /usr/lib/libX11.so.6
#3 0x00002ab214f4bcfb in gdk_event_prepare (source=<value optimized out>, 
timeout=<value optimized out>)
at /build/buildd/gtk+2.0-2.12.9/gdk/x11/gdkevents-x11.c:2308
#4 0x00002ab2160ac967 in IA__g_main_context_prepare (context=0x9fc100, 
priority=0x7fff994441c4) at /tmp/buildd/glib2.0-2.16.3/glib/gmain.c:2329
#5 0x00002ab2160ad028 in g_main_context_iterate (context=0x9fc100, block=1, 
dispatch=1, self=<value optimized out>)
at /tmp/buildd/glib2.0-2.16.3/glib/gmain.c:2622
#6 0x00002ab2160ad657 in IA__g_main_loop_run (loop=0xd0ebd0) 
at /tmp/buildd/glib2.0-2.16.3/glib/gmain.c:2850
#7 0x00002ab214a90b63 in IA__gtk_main () 
at /build/buildd/gtk+2.0-2.12.9/gtk/gtkmain.c:1163
#8 0x00002ab211d5b4e1 in wxEventLoop::Run () 
from /usr/lib/libwx_gtk2u_core-2.6.so.0
#9 0x00002ab211de2c2b in wxAppBase::MainLoop () 
from /usr/lib/libwx_gtk2u_core-2.6.so.0
#10 0x0000000000659723 in WinEDA_App::OnRun (this=0x9fbf50) 
at /home/rasasi/debs/kicad/pkg/kicad/common/edaappl.cpp:674
#11 0x00002ab21190aeec in wxEntry () from /usr/lib/libwx_baseu-2.6.so.0
#12 0x00000000005a5f0e in main (argc=2, argv=0x7fff99444448) 
at /home/rasasi/debs/kicad/pkg/kicad/pcbnew/pcbnew.cpp:29

Following this trace, I found that the loop occurred at IA__g_main_loop_run.

I haven't programmed on WxWidgets or gtk and I don't know if this behaviour 
is expected. I find strange taking full cpu permanently even when using the 
Debug build for no apparent reason.

I'd appreciate some clarification.

Best regards,
-- 
Raúl Sánchez Siles
 --nextPart3594694.mFURNFzWH0 Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part.

[Attachment content not displayed.] --nextPart3594694.mFURNFzWH0--




Follow ups