← Back to team overview

yade-users team mailing list archive

Re: [Question #679428]: unable to display sphere with latest version

 

Question #679428 on Yade changed:
https://answers.launchpad.net/yade/+question/679428

    Status: Answered => Open

Luc OGER is still having a problem:

I have erased all links to qt4 and compile libQGLViewer for qt5 and qmake-qt5
The program still crashes at the same "view 3D" choice....

the last line is :
/tmp/yade-Debt3H/tmp-0:3: Error in sourced command file:
Invalid thread ID: info
(gdb)
i don't even understand the term info for the thread ID ???

if I ask for the "info thread" i got this: Id   Target Id                                           Frame
* 1    Thread 0x7f0ffc4084c0 (LWP 30222) "yade-2019-04-26" 0x00007f0ffb8d1dd7 in waitpid () from /lib64/libc.so.6
  2    Thread 0x7f0fd827b700 (LWP 30227) "WorkerThread"    0x00007f0ffbbd6246 in do_futex_wait.constprop () from /lib64/libpthread.so.0
  3    Thread 0x7f0fd7a7a700 (LWP 30228) "WorkerThread"    0x00007f0ffbbd6246 in do_futex_wait.constprop () from /lib64/libpthread.so.0
  4    Thread 0x7f0fc4b1a700 (LWP 30229) "yade-2019-04-26" 0x00007f0ffbbd38ad in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
  5    Thread 0x7f0fbcd1c700 (LWP 30230) "llvmpipe-0"      0x00007f0ffbbd38ad in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
  6    Thread 0x7f0fbc51b700 (LWP 30231) "llvmpipe-1"      0x00007f0ffbbd38ad in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
  7    Thread 0x7f0fbbd1a700 (LWP 30232) "llvmpipe-2"      0x00007f0ffbbd38ad in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
  8    Thread 0x7f0fbb519700 (LWP 30233) "llvmpipe-3"      0x00007f0ffbbd38ad in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
  9    Thread 0x7f0fbad18700 (LWP 30234) "llvmpipe-4"      0x00007f0ffbbd38ad in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
  10   Thread 0x7f0fba517700 (LWP 30235) "llvmpipe-5"      0x00007f0ffbbd38ad in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
  11   Thread 0x7f0fb9d16700 (LWP 30236) "llvmpipe-6"      0x00007f0ffbbd38ad in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
  12   Thread 0x7f0fb9515700 (LWP 30237) "llvmpipe-7"      0x00007f0ffbbd38ad in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
  13   Thread 0x7f0f9a303700 (LWP 30435) "QXcbEventReader" 0x00007f0ffb8fa0bb in poll () from /lib64/libc.so.6
  14   Thread 0x7f0f98bf1700 (LWP 30436) "yade-2019-04-26" 0x00007f0ffbbd6246 in do_futex_wait.constprop () from /lib64/libpthread.so.0
  15   Thread 0x7f0f87bf4700 (LWP 30437) "QDBusConnection" 0x00007f0ffb8fa0bb in poll () from /lib64/libc.so.6
  16   Thread 0x7f0f8733a700 (LWP 30438) "llvmpipe-0"      0x00007f0ffbbd38ad in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
  17   Thread 0x7f0f86b39700 (LWP 30439) "llvmpipe-1"      0x00007f0ffbbd38ad in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
  18   Thread 0x7f0f86338700 (LWP 30440) "llvmpipe-2"      0x00007f0ffbbd38ad in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
  19   Thread 0x7f0f85b37700 (LWP 30441) "llvmpipe-3"      0x00007f0ffbbd38ad in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
  20   Thread 0x7f0f85336700 (LWP 30442) "llvmpipe-4"      0x00007f0ffbbd38ad in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
  21   Thread 0x7f0f84b35700 (LWP 30443) "llvmpipe-5"      0x00007f0ffbbd38ad in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
  22   Thread 0x7f0f6ffff700 (LWP 30444) "llvmpipe-6"      0x00007f0ffbbd38ad in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
  23   Thread 0x7f0f6f7fe700 (LWP 30445) "llvmpipe-7"      0x00007f0ffbbd38ad in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
  24   Thread 0x7f0f6effd700 (LWP 30452) "yade-2019-04-26" 0x00007f0ffb8fbf33 in select () from /lib64/libc.so.6


this looks to be a problem for a pthread but I have no idea where to look inside ou avoid this?

-- 
You received this question notification because your team yade-users is
an answer contact for Yade.