From: Tom Tromey <tom@tromey.com>
To: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
Cc: Tom de Vries <tdevries@suse.de>,
Simon Marchi <simon.marchi@efficios.com>,
Simon Marchi <simark@simark.ca>
Subject: Re: [PATCH v2] gdb: make "start" breakpoint inferior-specific
Date: Wed, 16 Nov 2022 09:22:16 -0700 [thread overview]
Message-ID: <875yfevphj.fsf@tromey.com> (raw)
In-Reply-To: <0a9685a1-805b-2212-9464-e5278ec05279@simark.ca> (Simon Marchi via Gdb-patches's message of "Mon, 14 Nov 2022 08:19:45 -0500")
>>>>> "Simon" == Simon Marchi via Gdb-patches <gdb-patches@sourceware.org> writes:
Simon> What is "set language unknown" useful for, generally speaking? If
Simon> debugging something in a language GDB doesn't know about, I think it
Simon> will fall back to minimal. Could we just not expose the "unknown"
Simon> language to the user?
I wonder if we can remove it entirely and replace it with "minimal".
Tom
next prev parent reply other threads:[~2022-11-16 16:22 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 17:40 [PATCH] " Simon Marchi
2022-08-17 17:56 ` Simon Marchi
2022-08-31 14:03 ` Bruno Larsen
2022-11-04 16:52 ` Simon Marchi
2022-11-07 8:14 ` Bruno Larsen
2022-11-08 17:24 ` Tom Tromey
2022-09-01 10:42 ` Andrew Burgess
2022-11-04 17:24 ` Simon Marchi
[not found] ` <8735asb7cj.fsf@redhat.com>
2022-11-09 13:19 ` Simon Marchi
2022-11-08 19:43 ` Pedro Alves
2022-11-08 20:14 ` Simon Marchi
2022-11-08 21:09 ` Pedro Alves
2022-11-08 21:20 ` [PATCH v2] " Simon Marchi
2022-11-10 16:45 ` Pedro Alves
2022-11-10 17:33 ` Simon Marchi
2022-11-10 17:36 ` Simon Marchi
2022-11-10 17:47 ` Pedro Alves
2022-11-10 17:53 ` Simon Marchi
2022-11-11 12:37 ` Tom de Vries
2022-11-11 13:53 ` Simon Marchi
2022-11-11 15:21 ` Tom de Vries
2022-11-11 19:03 ` Simon Marchi
2022-11-12 10:43 ` Tom de Vries
2022-11-14 11:29 ` Tom de Vries
2022-11-14 13:19 ` Simon Marchi
2022-11-14 14:18 ` Tom de Vries
2022-11-16 16:22 ` Tom Tromey [this message]
2022-11-16 16:26 ` Simon Marchi
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=875yfevphj.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
--cc=simon.marchi@efficios.com \
--cc=tdevries@suse.de \
/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).