[Bug gdb/17520] structure offset wrong when 1/4 GB or greater

["dtaylor at usendtaylorx2l dot lss.emc.com" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=17520

--- Comment #4 from dtaylor at usendtaylorx2l dot lss.emc.com ---
jan.kratochvil at redhat dot com <sourceware-bugzilla@sourceware.org> wrote:

> https://sourceware.org/bugzilla/show_bug.cgi?id=17520
> 
> --- Comment #3 from Jan Kratochvil <jan.kratochvil at redhat dot com> ---
> I do not know how to verify they are correct.  That is there is no accidental
> 32bitvar=64bitvar; assignment or similar.  While that may be possible with some
> LLVM static analysis I have been waiting for C++ which would make it easier. 
> But then we are (were) all waiting on that approval of C++ switch.
> 
> -- 
> You are receiving this mail because:
> You reported the bug.

I don't care whether it's my patch or Red Hat's or someone else's, so
long as the bug is fixed.

The bug affects us and we want it fixed.  I would rather not have to
reapply the patch for each release.

If problems are found with the patch, generally they are easy to fix --
find the ooffending variable and change it from int to LONGEST.

I configured GDB with --enable-werror.  I started by changing everything
that I cou8ld find that was going to cause problems and then iterated
until everything built and ran with no regressions.

There a couple of places where I wasn't certain that it needed to be
converted, but I figured better safe than sorry.

If people are truly worried about it destabilizing GDB, then the right
approach is to put it in early -- to get as much mileage as possible on
it before the next release.

With regard to GDB moving to C++ -- it might happen, it has certainly
been talked about on and off for enough years, but as whether it will
ever happen -- who knows.  But, I am not going hold my breath.

-- 
You are receiving this mail because:
You are on the CC list for the bug.