Problem in dynamically loading libraries

Hi Morix,

From your log I can see a lot of libraries not found. Please make sure these libraries are present on your system.

Best regards,
Miroslav

Yes, sure!

I see that a lot of log entries complaining about missin libraries but I think it depends on the set of paths attempted by the system for locating the libraries...

Anyway at least the library causing the problem (libicudata.so.52) is found in "/opt/icu/lib" (in fact the system opens and read it) but then suddenly exits with exit_group(1).

Who is calling exit_group(1)? Is there a way to determine why exit_group(1) is being called?

Regards,
/Morix

Morix, do a "man exit_group" to find out more about this system call.

Please let me know which AM335x SDK are you using and what toolchain did you use to cross-compile your Qt libraries and your Qt application?

Best regards,
Miroslav

Hi Miroslav,

I am using ti-sdk-am335x-evm-06.00.00.00 and I cross-compiled Qt 5.2.1 & my application using the toolchain included in the SDK (ti-sdk-am335x-evm-06.00.00.00/linux-devkit/sysroots/i686-arago-linux).

Ok for the manual page of "exit_group": I know its meaning... but my question was different: is it possible to understand which piece of code is calling "exit_group(1)" causing the application exit? I mean: there is a way for determining, for example, if the problem is in Qt or in ICU library?

Regards,
/Morix

As far as I know gdb can stop at system calls, so perhaps you can use it to debug your code, but I have never done this, so I can't help you there.

I believe the gdb command to do this is "catch syscall".

You can also post about your issue in the Beagle community as I believe there are people who had successfully built Qt5 for the am335x.

Best regards,
Miroslav

Thanks Miroslav,
I am going to try something about "catch syscall" in GDB... I'll let you know if I discover something useful.

At the same time I follow your advice to post my issue in the Beagle community forums: maybe somebody there can help me (here is the link in case someone is interested in following the discussion: http://beagleboard.org/Community/Forums?place=topic%2Fbeagleboard%2F-BY4H6RC8W4%2Fdiscussion).

Thanks & regards.
/Morix

Miroslav,
I've still got a question: it seems that "catch syscall" is not supported in "arm-linux-gnueabihf-gdb" yet... Here is what it says:

(gdb) catch syscall
The feature 'catch syscall' is not supported on this architecture yet.

Any other suggestions?

/Morix

Miroslav,
I determined that the problem is definitively due to ICU library (the same problem shows up simply launching the "icuinfo" tool provided together with the library).

Hence I refactored the question and published it under a new title here.

Regards,
/Morix