|
From: | Orc Erc |
Subject: | Re: lt_dlopen no return |
Date: | Tue, 16 Dec 2014 12:42:08 +0200 |
Run your program under a debugger such as GDB. While it is stuck, do CONTROL-C on the keyboard and then then enter 'bt' at the GDB command-line. This should show where it is stuck.On Mon, 15 Dec 2014, Orc Erc wrote:
Hi All,
When i called the lt_dlopen function, it sticks. There is no return from that function.
Where do i look?
An alternative is to make sure that core dumps are properly enabled and then do
kill -QUIT pid
where pid is the process ID of the stuck process. You should then get a core dump of the program that you can investigate using a debugger.
If you need more help here, then you would need to tell us the libtool version you are using, and the operating system you are running it on.
Bob
--
Bob Friesenhahn
address@hidden, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
[Prev in Thread] | Current Thread | [Next in Thread] |