Hi On Sun, Feb 28, 2016 at 07:57:43PM +0100, Samuel Thibault wrote: > > Using watch in gdb :) > > I've added fprintf(stderr,"%p\n", &errno); to get the address of errno: >
Oh, that's interesting. I've been struggling with "display errno", or "display *__errno_location()" without success. > > Could you give that a try? Yes, I'll try in the following days. Also I've been looking at the specification of dlopen and it doesn't say anything about errno and the only way to know what happened is the textual message given by dlerror. Thus, console-client is relying on undefined behaviour. Unfortunately, it seems the only standard way is to parse that textual message. :-( I guess console-client could be modified to try other directories in the search path regardless of the reason why dlopen failed. Diego
