From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id C94E939874C2; Sat, 26 Jun 2021 02:15:19 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C94E939874C2 From: "rincebrain at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug threads/28014] gdb coredumps when remote+kgdbing a system that OOMs too hard Date: Sat, 26 Jun 2021 02:15:19 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: threads X-Bugzilla-Version: 10.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: rincebrain at gmail 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: 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: Sat, 26 Jun 2021 02:15:19 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D28014 --- Comment #2 from Rich --- (In reply to Simon Marchi from comment #1) > Hi Rich, >=20 > (In reply to Rich from comment #0) > > I was using gdb on mips64el under qemu-user to remote a qemu of a mips6= 4el > > system with kgdb, everything was going fine (from gdb's perspective - t= he > > system was in the process of eating all the RAM), then things went sout= h. >=20 > Unrelated to the reported problem, but do you run GDB as a mips64el progr= am > inside qemu-user only so that you can debug your remote mips64el program?= =20 > It might be easier to run an x86-64 GDB (or whatever your host system is)= to > connect to your mips64el remote. That GDB just needs to be built to incl= ude > mips support, using --target=3D, or > --enable-targets=3D, or --enable-targets=3Dall. Yeah, but recompiling gdb with all the arches I might need is a timesink wh= en I already had a chroot right there, and Debian's definitely doesn't have other targets enabled OOTB. > It might not be a bug somebody will immediately jump to fix, but every ti= me > you hit a GDB internal error, you can consider it a valid GDB bug. It > should never be possible for a user to hit an internal error, whatever the > bad input they provide (including a remote connection breaking at an > unexpected moment).=20=20 Duly noted. That's nice; I've encountered all sorts of philosophies on that, and while the one you describe aligns with my own opinions on the matter, n= ot everyone agrees. > > Since the core is 80M compressed and 236M uncompressed, you can find it: > > https://www.dropbox.com/s/u7erpk1x6fj4ds6/qemu_gdb_20210625-192829_1845= 0. > > core.zst?dl=3D0 >=20 > There's little we can do without the gdb executable that goes along with = the > core file. Can you provide that too? If we can get a good backtrace of > GDB, at least we'll be able to rough idea. It's just the gdb binary from Debian bullseye at this precise moment: https://www.dropbox.com/s/orf6tmcbctpjx16/gdb?dl=3D0 You may find this pretty useless, as none of my gdbs find the core useful, = and so far nobody in #qemu has known how to make use of it either. --=20 You are receiving this mail because: You are on the CC list for the bug.=