Libtool error reporting.
Hi, As have been mentioned on the list, libtool error reporting - "file not found" is not perfect. People suggested to fix it (http://www.mail-archive.com/libtool@gnu.org/msg12156.html) but it seems, that the changes have never been incorporated into the trunk. I'm not well familiar with all the details of the problem, but I would suggest to improve the debug mode (-DLT_DEBUG_LOADERS) verbose messaging. Libtool already prints "Success/Failed", so I suggest to extend the message and print out the last error (LT__GETERROR(error)) for the Failed case. My 0,02$ Regards, Pavel (Pasha) Shamis ___ https://lists.gnu.org/mailman/listinfo/libtool
Re: Libtool error reporting.
Peter, Actually, I already have a patch. Please see attached file. It is very simple, if module opening fails, in addition to "Failed" message, it prints out last error message. So far it is only a spot where I found useful to add verbose error reporting. libtool_debug_error_reporting.patch Description: libtool_debug_error_reporting.patch Regards, Pavel (Pasha) Shamis --- Application Performance Tools Group Computer Science and Math Division Oak Ridge National Laboratory On Dec 8, 2011, at 12:19 AM, Peter O'Gorman wrote: > On 12/05/2011 11:48 AM, Shamis, Pavel wrote: >> Hi, >> >> As have been mentioned on the list, libtool error reporting - "file not >> found" is not perfect. People suggested to fix it >> (hxxp://www.mail-archive.com/libtool@gnu.org/msg12156.html) but it seems, >> that the changes have never been incorporated into the trunk. I'm not well >> familiar with all the details of the problem, but I would suggest to improve >> the debug mode (-DLT_DEBUG_LOADERS) verbose messaging. Libtool already >> prints "Success/Failed", so I suggest to extend the message and print out >> the last error (LT__GETERROR(error)) for the Failed case. > > This seems like a good idea (if DEBUG_LOADERS is defined, print the > error to stderr every time an error is set). If you don't come up with a > patch, I'll try to find the time to do it. > > Thanks, > Peter > > ___ https://lists.gnu.org/mailman/listinfo/libtool
Re: Libtool error reporting.
Peter, Did you have a chance to look at the patch. Please let me know if you have some comments. I found it extremely useful for debug of module component architecture, that loads modules on the "fly". Regards, Pavel (Pasha) Shamis --- Application Performance Tools Group Computer Science and Math Division Oak Ridge National Laboratory On Dec 8, 2011, at 11:09 AM, Shamis, Pavel wrote: > Peter, > > Actually, I already have a patch. Please see attached file. It is very > simple, if module opening fails, in addition to "Failed" message, it prints > out last error message. > So far it is only a spot where I found useful to add verbose error reporting. > > > > Regards, > > Pavel (Pasha) Shamis > --- > Application Performance Tools Group > Computer Science and Math Division > Oak Ridge National Laboratory > > On Dec 8, 2011, at 12:19 AM, Peter O'Gorman wrote: > >> On 12/05/2011 11:48 AM, Shamis, Pavel wrote: >>> Hi, >>> >>> As have been mentioned on the list, libtool error reporting - "file not >>> found" is not perfect. People suggested to fix it >>> (hxxp://www.mail-archive.com/libtool@gnu.org/msg12156.html) but it seems, >>> that the changes have never been incorporated into the trunk. I'm not well >>> familiar with all the details of the problem, but I would suggest to >>> improve the debug mode (-DLT_DEBUG_LOADERS) verbose messaging. Libtool >>> already prints "Success/Failed", so I suggest to extend the message and >>> print out the last error (LT__GETERROR(error)) for the Failed case. >> >> This seems like a good idea (if DEBUG_LOADERS is defined, print the >> error to stderr every time an error is set). If you don't come up with a >> patch, I'll try to find the time to do it. >> >> Thanks, >> Peter >> >> > > ___ > hxxps://lists.gnu.org/mailman/listinfo/libtool ___ https://lists.gnu.org/mailman/listinfo/libtool
