From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 6A601386F80C; Thu, 21 May 2020 19:00:49 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6A601386F80C From: "keiths at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug breakpoints/26019] FreeRTOS task breakpoint causes core dump Date: Thu, 21 May 2020 19:00:49 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: breakpoints X-Bugzilla-Version: 9.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: keiths at redhat dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gdb-prs@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-prs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 May 2020 19:00:49 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D26019 Keith Seitz changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |keiths at redhat dot com --- Comment #2 from Keith Seitz --- (In reply to Jeff Kent from comment #0) > Created attachment 12559 [details] > Core dump from GDB 9.1 >=20 > To reproducing the problem is an issue, because it requires specific > hardware. If needed I can provide GDB server and target reset access by > appointment. The source of the project can be found at > https://github.com/jkent/pollux-baremetal/tree/gdb-bug . That is going to slow things down a bit, yes. Is it a crash/abort or an assertion failure? Can you copy/paste your gdb session here demonstrating the problem? That mi= ght provide some insight into what's going on. > I think the next task would be to build GDB with debug symbols so the c= ore > dump can provide a useful backtrace. I do not know how to do this -- is > there a ./Configure option that can be passed to enable debugging? This > would be the easiest route, to build a new toolchain with crosstool-ng.=20 > Attached is the core dump. Here's my standard debug build configure line. [Note this will enable all target configurations.] You might change --prefix to point at a distinct installation directory, but you do not normally need to install gd= b to use it. I run from the objdir all the time. $ flags=3D"-g3 -O0" CFLAGS=3D"$flags" CXXFLAGS=3D"$flags" /path/to/configure --disable-binutils --disable-elfcpp --disable-gas --disable-gold --disable-gprof --disable-ld --enable-unit-tests --with-system-readline --with-separate-debug-dir=3D/usr/lib/debug --enable-targets=3Dall --with-lz= ma --prefix=3D/usr --with-separate-debug-dir=3D/usr/lib/debug --=20 You are receiving this mail because: You are on the CC list for the bug.=