Re: [microblaze-uclinux] more debugging problems, resent from gmail

[John Williams <jwilliams@xxxxxxxxxxxxxx>]

Hi Larry,

Westover Scientific wrote:
> The gdb debugger, as invoked by mb-uclinux-gdb, seems to have curious 
> pathing. For instance, when stepping into a destructor
> it paths out to:
>
>
> operator delete(void*) (ptr=0x2494ee18)
>     at 
> /mnt/home/jwilliam/PetaLogix/microblaze-toolchain-sources/srcs/gcc/libstdc++-v3/libsupc++/del_op.cc:39
> 39      
> /mnt/home/jwilliam/PetaLogix/microblaze-toolchain-sources/srcs/gcc/libstdc++-v3/libsupc++/del_op.cc: 
> No such file or directory.
>         in 
> /mnt/home/jwilliam/PetaLogix/microblaze-toolchain-sources/srcs/gcc/libstdc++-v3/libsupc++/del_op.cc
>
>
> I would have thought it should be somewhere in my petalinux rather than 
> referring to John's non-existent account.

The C++ libraries are precompiled and distributed in the toolchain, and 
the debugging symbols are therrefore referring to locations on my build 
server rather than your local setup.

The solution here is to not step into the libraries, instead use the 
"next" command instead of "step".  Alternateively, you can set a 
breakpoint in your aplication source code beyond the call to the library 
function, and then issue a "continue" command, which will run until that 
breakpoint.

Regards,

John
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/