From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18539 invoked by alias); 26 Nov 2012 21:33:25 -0000 Received: (qmail 18514 invoked by uid 48); 26 Nov 2012 21:33:25 -0000 From: "mgyucht at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug tui/14880] New: In split register layouts, `up` results in assertion failure in value.c Date: Mon, 26 Nov 2012 21:33:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: tui X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: mgyucht at gmail dot com X-Bugzilla-Status: NEW X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 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 X-SW-Source: 2012-q4/txt/msg00308.txt.bz2 http://sourceware.org/bugzilla/show_bug.cgi?id=14880 Bug #: 14880 Summary: In split register layouts, `up` results in assertion failure in value.c Product: gdb Version: 7.5 Status: NEW Severity: minor Priority: P2 Component: tui AssignedTo: unassigned@sourceware.org ReportedBy: mgyucht@gmail.com Classification: Unclassified Created attachment 6756 --> http://sourceware.org/bugzilla/attachment.cgi?id=6756 Executable which breaks gdb when trying to move up the stack frame in register split layouts In the TUI split register layouts, running the command 'up' results in the following error: (gdb) up value.c:549: internal-error: value_available_contents_eq: Assertion `!val1->lazy && !val2->lazy' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) At this point, I'm offered the chance to quit the debugging session and to create a core dump of gdb. This only happens in the asm/register or source/register split layouts; the behavior is normal with the other layouts. To reproduce, run the following commands: $ gdb p2 (gdb) b main (gdb) r (gdb) s (until you have moved into the addvec function source) (gdb) layout p (gdb) up This has happened on other files as well. In addition, p2 and its libraries (statically linked) were compiled using gcc. $ uname -a Linux miles 3.5.6-1-ARCH #1 SMP PREEMPT Sun Oct 7 19:30:49 CEST 2012 x86_64 GNU/Linux $ gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-unknown-linux-gnu/4.7.2/lto-wrapper Target: x86_64-unknown-linux-gnu Configured with: /build/src/gcc-4.7.2/configure --prefix=/usr --libdir=/usr/lib --libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=https://bugs.archlinux.org/ --enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++ --enable-shared --enable-threads=posix --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-clocale=gnu --disable-libstdcxx-pch --enable-libstdcxx-time --enable-gnu-unique-object --enable-linker-build-id --with-ppl --enable-cloog-backend=isl --disable-ppl-version-check --disable-cloog-version-check --enable-lto --enable-gold --enable-ld=default --enable-plugin --with-plugin-ld=ld.gold --with-linker-hash-style=gnu --enable-multilib --disable-libssp --disable-build-with-cxx --disable-build-poststage1-with-cxx --enable-checking=release Thread model: posix gcc version 4.7.2 (GCC) $ gdb --version GNU gdb (GDB) 7.5 Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-unknown-linux-gnu". For bug reporting instructions, please see: . -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.