Either you aren't building your executable with -g, or you aren't linking against the debug library. Or the flags were insufficient and the library didnt get built with -g. The way to proceed is to make verbose=1 ; or similar, to verify by inspection that the -g is being applied at each compilation step. On Jan 14, 2014, at 3:13 PM, Laurent Alebarde <l.alebarde@xxxxxxx> wrote: > I still don't manage to have the debugger working correctly onto nanomsg: > http://stackoverflow.com/questions/21119129/my-debug-build-under-linux-gcc-is-missing-symbol-information-for-some-of-them > > Without a debugger, I cannot progress. As I am on a time frame, I won't be > able to fight too much longer with that. Any advice would be of great help. > > Le 14/01/2014 16:58, Laurent Alebarde a écrit : >> Hi, >> >> I am building nanomsg with: >> >> nanomsg $ make distclean >> nanomsg $ ./autogen.sh >> nanomsg $ cd Debug >> Debug $ ../configure --prefix=/Debug CPPFLAGS=-DDEBUG CFLAGS="-O0 -g3 -Wall" >> Debug $ make >> Debug $ make check >> >> All 29 tests passed >> >> But when I debug tests/reqrep, I can go into test_socket which as a macro >> expends to test_socket_impl, but when inside >> test_socket_impl, I cannot go inside nn_socket for example. >> >> The debugger says: "no debug info" >> >> Any idea please ? >