From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10218 invoked by alias); 24 Nov 2014 21:32:20 -0000 Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-prs-owner@sourceware.org Received: (qmail 10183 invoked by uid 55); 24 Nov 2014 21:32:18 -0000 From: "dtaylor at usendtaylorx2l dot lss.emc.com" To: gdb-prs@sourceware.org Subject: [Bug gdb/17520] structure offset wrong when 1/4 GB or greater Date: Mon, 24 Nov 2014 21:32:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 7.8 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dtaylor at usendtaylorx2l dot lss.emc.com X-Bugzilla-Status: NEW X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-q4/txt/msg00310.txt.bz2 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 wrote: > https://sourceware.org/bugzilla/show_bug.cgi?id=17520 > > --- Comment #3 from Jan Kratochvil --- > 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.