Debugging across uClibc calls

Rob Landley rob at
Wed Jul 4 02:33:38 UTC 2007

On Monday 02 July 2007 14:15:32 Ken Cecka wrote:
> Originally posted this on the buildroot list, but they directed me here...
> Hi All,
> I've got a PPC405 target up and running with a buildroot/uClibc linux


> environment, and now I'm trying to debug an application.  I can launch the
> application using gdbserver and then connect to it using my host gdb, and
> everything is great as I step through the code... until I reach a C
> library
> call.  Any time I try to step over one of these (e.g. print, memcpy, etc),
> I end up getting stuck in call___do_global_ctors_aux.

I believe that's a gcc symbol, grep found it in /usr/lib/gcc/*/*/crtend.o

> I did a little searching around on the web and the only thing I could find
> about this is that this symbol is related to runtime linking of shared
> library functions.  That's fine and dandy, but how do I get past it?  I'm
> not trying to step into the call, just over it so I can continue debugging
> my high level code.
> Any suggestions?

Sounds like your debugger's a bit weird.

> Thanks,
> Ken

"One of my most productive days was throwing away 1000 lines of code."
  - Ken Thompson.

More information about the uClibc mailing list