public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "rincebrain at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug threads/28014] New: gdb coredumps when remote+kgdbing a system that OOMs too hard
Date: Fri, 25 Jun 2021 23:43:13 +0000	[thread overview]
Message-ID: <bug-28014-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 28014
           Summary: gdb coredumps when remote+kgdbing a system that OOMs
                    too hard
           Product: gdb
           Version: 10.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: threads
          Assignee: unassigned at sourceware dot org
          Reporter: rincebrain at gmail dot com
  Target Milestone: ---

I was using gdb on mips64el under qemu-user to remote a qemu of a mips64el
system with kgdb, everything was going fine (from gdb's perspective - the
system was in the process of eating all the RAM), then things went south.

The kernel reported, after a whole bunch of other screaming:
[59702.844702] Out of memory and no killable processes...
[59702.845130] Kernel panic - not syncing: System is deadlocked on memory

Meanwhile, when I tabbed back over, gdb said:
[New Thread 172398]
[New Thread 172401]
[New Thread 172402]
[New Thread 172403]
[New Thread 172404]
[New Thread 172405]
--Type <RET> for more, q to quit, c to continue without paging--

Thread 2 received signal SIGTRAP, Trace/breakpoint trap.
[Switching to Thread 1]
/build/gdb-OSO7kB/gdb-10.1/gdb/thread.c:95: internal-error: thread_info*
inferior_thread(): Assertion `current_thread_ != nullptr' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) y

This is a bug, please report it.  For instructions, see:
<https://www.gnu.org/software/gdb/bugs/>.

/build/gdb-OSO7kB/gdb-10.1/gdb/thread.c:95: internal-error: thread_info*
inferior_thread(): Assertion `current_thread_ != nullptr' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) y
qemu: uncaught target signal 6 (Aborted) - core dumped
Aborted


And so I'm here.

(I won't be astonished if you just close this with "everything was on fire,
what are you expecting", but since gdb did request I open a bug, here I am.)

Since the core is 80M compressed and 236M uncompressed, you can find it:
https://www.dropbox.com/s/u7erpk1x6fj4ds6/qemu_gdb_20210625-192829_18450.core.zst?dl=0

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

             reply	other threads:[~2021-06-25 23:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-25 23:43 rincebrain at gmail dot com [this message]
2021-06-26  1:20 ` [Bug threads/28014] " simark at simark dot ca
2021-06-26  2:15 ` rincebrain at gmail dot com
2021-06-26  2:29 ` simark at simark dot ca
2021-06-26  2:41 ` rincebrain at gmail dot com
2021-06-26  4:27 ` simark at simark dot ca
2021-06-26 10:55 ` rincebrain at gmail dot com
2021-06-26 13:04 ` simark at simark dot ca
2021-06-27  5:27 ` simark at simark dot ca
2021-06-27 12:24 ` rincebrain at gmail dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-28014-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).