I'm having some problems with static data members and gdb. (This would
be current sourceware GDB, via the 'src' repository on RH 6.2/x86)
To get the ball rolling, I've made a simple test case:
struct __ios_flags
{
typedef short __int_type;
static const __int_type _S_boolalpha = 1
Not our fault, the debug info is wrong, or it really is optimized out.
It doesn't give us either a bit offset, or the data member location inside
the struct, or a place where we can find them.
So GDB, rightfully, assumed it's optimized out (because it has no
location, and thus, doesn't exist).
It
Daniel Berlin wrote:
>
> Not our fault, the debug info is wrong, or it really is optimized out.
> It doesn't give us either a bit offset, or the data member location inside
> the struct, or a place where we can find them.
> So GDB, rightfully, assumed it's optimized out (because it has no
> locat
On Thu, 31 Aug 2000, Andrew Cagney wrote:
>
> Just BTW, if the debug info is corrupt then GDB should report an error()
> and not an internal_error(). Internal errors are more for when gdb's
> internal data structures turn out to be broken (and about to core dump
> :-).
>
> enjoy,
>
