Diego Nieto Cid, on Sun 28 Feb 2016 16:53:51 -0300, wrote: > 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.
It's a TLS variable, and gdb hasn't been taught how to reach them yet. > > Could you give that a try? > > Yes, I'll try in the following days. Thanks. > 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. Yes. That's the spec. AIUI, glibc does better and the hurd console uses it :) Samuel
