public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "nkulikov at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug server/28822] New: sh4 gdbserver crash
Date: Wed, 26 Jan 2022 14:59:08 +0000	[thread overview]
Message-ID: <bug-28822-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 28822
           Summary: sh4 gdbserver crash
           Product: gdb
           Version: 11.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: server
          Assignee: unassigned at sourceware dot org
          Reporter: nkulikov at gmail dot com
  Target Milestone: ---

gdbserver crashes when gdb is connecting to remote (couple printfs added to
dump variables):

$  ./gdbserver :55555 /bin/ls
Process /bin/ls created; pid = 1356
Listening on port 55555
Remote debugging from host 192.168.254.44, port 45206
current_thread = 0x48a5e8                           <- extra printf
tdesc->xmltarget = (nil)                            <- extra printf
tdesc->features.empty = 0, tdesc->arch = (nil)      <- extra printf
tdesc.cc:200: A problem internal to GDBserver has been detected.
const char* tdesc_get_features_xml(const target_desc*): Assertion
`tdesc->xmltarget != NULL || (!tdesc->features.empty () && tdesc->arch !=
NULL)' failed.

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

             reply	other threads:[~2022-01-26 14:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-26 14:59 nkulikov at gmail dot com [this message]
2022-01-27 13:01 ` [Bug server/28822] " aburgess at redhat dot com
2022-01-27 17:23 ` nkulikov at gmail dot com
2022-01-27 17:24 ` nkulikov 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-28822-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).