Re: single-step problems

[emure]

Benoit Hudson wrote:

> Since upgrading to 5.0, I've had the pleasure of being able to debug my C++
> code (under 4.18 any call made gdb dump core).
>
> Unfortunately, I've often lost the ability of stepping into a function.  I
> hit 's' and usually (but not always) it just goes to the next line.  I
> would expect this (and I do see it) when compiling with optimization, but
> it also happens without optimization.  Have others experienced this?
> I haven't been able to isolate this to a small case unfortunately.
>
> The workaround is just to set a breakpoint in the function I want to step
> into.
>
> My platform:
>     sparc-sun-solaris2.6
>     gcc 2.95.2
>     gdb 5.0
>
> I compile with for instance:
>   gcc -c -g -Wall -Werror -DHAVE_CONFIG_H -I../include \
>     Solver.c  -fPIC -DPIC -o Solver.lo
>   c++ -c -g -Wall -Wno-non-virtual-dtor -Werror -DHAVE_CONFIG_H -I../include \
>     trace.cc  -fPIC -DPIC -o trace.lo
>
> (there are 1000 some files so I'll spare you the details).
>         -- Benoît

Hi,
Recently, a patch added a set-step-mode feature
to enable gdb to step into a function without debug informations
Perhaps, it's what you need... (For assembly language reader)