[atg]

A couple of messages. Are these a problem to be solved, or ignored?

1. Whenever I start Engrid, I get a bunch of these messages in the terminal:

karl@home-linux:~$ engrid
void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action "" under id 59
m_LogFileName = /tmp/enGrid_20130806131638629/enGrid_output.txt
QObject: Cannot create children for a parent that is in a different thread.
(Parent is GuiMainWindow(0x7fff9692eac0), parent's thread is QThread(0x1d70610), current thread is QThread(0x19738078)
QObject: Cannot create children for a parent that is in a different thread.
(Parent is GuiMainWindow(0x7fff9692eac0), parent's thread is QThread(0x1d70610), current thread is QThread(0x19738078)
QObject: Cannot create children for a parent that is in a different thread.
(Parent is GuiMainWindow(0x7fff9692eac0), parent's thread is QThread(0x1d70610), current thread is QThread(0x19738078)
QObject: Cannot create children for a parent that is in a different thread.
(Parent is GuiMainWindow(0x7fff9692eac0), parent's thread is QThread(0x1d70610), current thread is QThread(0x19738078)
QObject: Cannot create children for a parent that is in a different thread.
(Parent is GuiMainWindow(0x7fff9692eac0), parent's thread is QThread(0x1d70610), current thread is QThread(0x19738078)
QObject: Cannot create children for a parent that is in a different thread.
(Parent is GuiMainWindow(0x7fff9692eac0), parent's thread is QThread(0x1d70610), current thread is QThread(0x19738078)
QObject: Cannot create children for a parent that is in a different thread.
(Parent is GuiMainWindow(0x7fff9692eac0), parent's thread is QThread(0x1d70610), current thread is QThread(0x19738078)
QObject: Cannot create children for a parent that is in a different thread.
(Parent is GuiMainWindow(0x7fff9692eac0), parent's thread is QThread(0x1d70610), current thread is QThread(0x19738078)
QObject: Cannot create children for a parent that is in a different thread.
(Parent is GuiMainWindow(0x7fff9692eac0), parent's thread is QThread(0x1d70610), current thread is QThread(0x19738078)
QObject: Cannot create children for a parent that is in a different thread.
(Parent is GuiMainWindow(0x7fff9692eac0), parent's thread is QThread(0x1d70610), current thread is QThread(0x19738078)

2. Fairly often, I get this message after meshing the same file for awhile, which results in a crash:

No projection found for point, id_node= 125643 , xp= inf inf -inf

m_G1= (-inf, -inf, inf)
m_G2= (-inf, -inf, inf)
m_G3= (nan, nan, nan)
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
Xlib: sequence lost (0x24383 > 0x14385) in reply type 0x1c!
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
[xcb] Unknown request in queue while dequeuing
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
engrid: ../../src/xcb_io.c:179: dequeue_pending_request: Assertion `!xcb_xlib_unknown_req_in_deq' failed.
/home/karl/Software/engrid/run.bash: line 26: 6367 Aborted (core dumped) $dir/src/engrid

I know there are other ways to report bugs, but I am wondering if these messages are particular to my installation, or if others have them also?

Thanks,
Karl

[wyldckat]

Greetings Karl,

This:

QObject: Cannot create children for a parent that is in a different thread.

is a clear indication that the standard building procedure was not followed to the letter

Which enGrid version are you building and which instructions are you following? Because those errors are related to building enGrid in Debug mode and/or with QT threading activated.

Best regards,
Bruno

[atg]

Originally Posted by wyldckat

Greetings Karl,

Which enGrid version are you building and which instructions are you following? Because those errors are related to building enGrid in Debug mode and/or with QT threading activated.

I'm just using the quick and dirty method suggested by Elvis on the other thread. So it's 1.4. It seems to work ok except for these errors, which I was ignoring until it started crashing for some reason (probably unrelated judging from your comment).


Thanks Much,
Karl

[wyldckat]

Hi Karl,

I forgot to ask: which Linux Distribution are you using? I want to check if I can reproduce this issue.

Best regards,
Bruno

[atg]

Originally Posted by wyldckat

Hi Karl,

I forgot to ask: which Linux Distribution are you using? I want to check if I can reproduce this issue.

Best regards,
Bruno

I think I may have pulled the master branch instead of release-1.4. I often change that in the script when I update.


I reinstalled master last night and the Qt messages went away! Maybe the branch changed. Thanks for your help.


Ubuntu 12.04 LTS.

--edit-- oops, the message about the threads is still there. Master branch.

[wyldckat]

Hi Karl,

Ah, nothing like living on the bleeding edge of enGrid

OK, I've tried just now the following steps on two machines (one real and one virtual) Ubuntu 12.04 x86_64, with BrlCad installed from the Deb package located here: http://sourceforge.net/projects/brlc...0Linux/7.24.0/
And ran the following command for activating the respective environment variable:

export BRLCADINCDIR=/usr/brlcad/include
export BRLCADLIBDIR=/usr/brlcad/lib

Then, from within the "engrid/src" folder:

source scripts/setup_pathes.bash
make clean
rm Makefile* libengrid/Makefile* netgen_svn/Makefile*
scripts/build-nglib.sh
qmake
make -j 4

FYI, the "Makefile*" files are generated by qmake. The 4 can be changed to 6 or 8, depending on the number of cores your machine has got.

But the problem is that it failed to build, with the following messages:

./libengrid/libengrid.so: undefined reference to `nglib::Ng_NewMesh()'
./libengrid/libengrid.so: undefined reference to `typeinfo for netgen::NgException'
./libengrid/libengrid.so: undefined reference to `nglib::Ng_GetPoint(void**, int, double*)'
./libengrid/libengrid.so: undefined reference to `nglib::Ng_GetNE(void**)'
./libengrid/libengrid.so: undefined reference to `nglib::Ng_GetSurfaceElement(void**, int, int*)'
./libengrid/libengrid.so: undefined reference to `vtable for netgen::NgException'
./libengrid/libengrid.so: undefined reference to `nglib::Ng_Meshing_Parameters::Ng_Meshing_Parameters()'
./libengrid/libengrid.so: undefined reference to `nglib::Ng_GenerateVolumeMesh(void**, nglib::Ng_Meshing_Parameters*)'
/usr/lib/x86_64-linux-gnu/libavcodec.so.53: undefined reference to `deflateBound@ZLIB_1.2.0'
./libengrid/libengrid.so: undefined reference to `nglib::Ng_DeleteMesh(void**)'
./libengrid/libengrid.so: undefined reference to `nglib::Ng_GetNSE(void**)'
./libengrid/libengrid.so: undefined reference to `nglib::Ng_AddPoint(void**, double*)'
./libengrid/libengrid.so: undefined reference to `netgen::NgException::~NgException()'
./libengrid/libengrid.so: undefined reference to `nglib::Ng_Init()'
./libengrid/libengrid.so: undefined reference to `nglib::Ng_GetVolumeElement(void**, int, int*)'
./libengrid/libengrid.so: undefined reference to `nglib::Ng_Exit()'
./libengrid/libengrid.so: undefined reference to `nglib::Ng_AddSurfaceElement(void**, nglib::Ng_Surface_Element_Type, int*)'
./libengrid/libengrid.so: undefined reference to `nglib::Ng_RestrictMeshSizeBox(void**, double*, double*, double)'
./libengrid/libengrid.so: undefined reference to `nglib::Ng_GetNP(void**)'
/usr/lib/x86_64-linux-gnu/libxml2.so.2: undefined reference to `gzdirect@ZLIB_1.2.2.3'

Therefore, I estimate that you are using a mixed version of enGrid, where the main binary "engrid" is an old build and the library "libengrid/libengrid.so" is based on the new source code. Which perhaps would explain the unusual issue you're getting.

I'll see if I can figure out how to solve this in some 12h from now.

Best regards,
Bruno

[wyldckat]

Hi Karl,

I finally managed to have the time and figure out the problem on my side. From what I can figure out, the same hasn't happened to you and Oliver it's possibly because the "Makefile" files weren't updated (for those interested, it's fixed in this commit: https://github.com/enGits/engrid/com...e75294868d84bb ).

Anyway, now I'm in a position to help diagnose the problem. Please run the following commands from the folder "engrid/src":

export LD_LIBRARY_PATH=./libengrid:./netgen_svn:$LD_LIBRARY_PATH:/usr/brlcad/lib

ldd engrid > ldd_engrid.txt 2>&1

Attached is the file "ldd_engrid.txt" I got from the previous command. This gives us a good indication of the libraries that are being used for the enGrid application. My guess is that there is a bad link happening somewhere.

Best regards,
Bruno

[atg]

Originally Posted by wyldckat

Hi Karl,

I finally managed to have the time and figure out the problem on my side. From what I can figure out, the same hasn't happened to you and Oliver it's possibly because the "Makefile" files weren't updated (for those interested, it's fixed in this commit: https://github.com/enGits/engrid/com...e75294868d84bb ).

Anyway, now I'm in a position to help diagnose the problem. Please run the following commands from the folder "engrid/src":

export LD_LIBRARY_PATH=./libengrid:./netgen_svn:$LD_LIBRARY_PATH:/usr/brlcad/lib

ldd engrid > ldd_engrid.txt 2>&1

Attached is the file "ldd_engrid.txt" I got from the previous command. This gives us a good indication of the libraries that are being used for the enGrid application. My guess is that there is a bad link happening somewhere.

Best regards,
Bruno

Thanks Bruno I'll take a look at it this weekend.