public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug remote/27768] Connecting to debugserver fails
Date: Fri, 23 Apr 2021 14:49:12 +0000 [thread overview]
Message-ID: <bug-27768-4717-NNFQPTOGgr@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27768-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27768
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at sourceware dot org
Target| |*-*-darwin*
--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
lldb extended the gdb remote protocol stop replies.
https://github.com/llvm/llvm-project/blob/main/lldb/docs/lldb-gdb-remote.txt
// We have extended the "T" packet to be able to also understand the
// following keys and values:
...
// "metype" unsigned mach exception type (the value of the EXC_XXX
enumerations)
// as an unsigned integer. For targets with mach
// kernels only.
[...etc...]
Unfortunate that they chose not to have this be probed.
Some work in remote.c would be needed to handle these.
Also:
> warning: Architecture rejected target-supplied description
gdb's Darwin tdep code doesn't seem to handle XML target descriptions.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2021-04-23 14:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 19:03 [Bug remote/27768] New: " jrmuizel at gmail dot com
2021-04-23 14:49 ` tromey at sourceware dot org [this message]
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-27768-4717-NNFQPTOGgr@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).