Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
To: Tom Tromey <tom@tromey.com>,
	Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
Cc: Tom de Vries <tdevries@suse.de>, Simon Marchi <simark@simark.ca>
Subject: Re: [PATCH v2] gdb: make "start" breakpoint inferior-specific
Date: Wed, 16 Nov 2022 11:26:46 -0500	[thread overview]
Message-ID: <cd5acab3-c67d-288e-8d13-69d75aa31abb@efficios.com> (raw)
In-Reply-To: <875yfevphj.fsf@tromey.com>

On 11/16/22 11:22, Tom Tromey wrote:
>>>>>> "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

I think so.  I started a patch here [1] but haven't had time to follow
up on it.

In the uses of "set lang unknown" in the testsuite, two are to verify
that trying to print an expression while the unknown language is
selected gives an error message and does not crash, we don't care about
those.

The other one, in gdb.cp/demangle.exp, I think it's to make sure that
the current language is something else than the language we pass to
"demangle -l".  I think using the minimal language there should be fine.

Simon

[1] https://review.lttng.org/c/binutils-gdb/+/8952

      reply	other threads:[~2022-11-16 16:27 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-04 17:40 [PATCH] " Simon Marchi via Gdb-patches
2022-08-17 17:56 ` Simon Marchi via Gdb-patches
2022-08-31 14:03 ` Bruno Larsen via Gdb-patches
2022-11-04 16:52   ` Simon Marchi via Gdb-patches
2022-11-07  8:14     ` Bruno Larsen via Gdb-patches
2022-11-08 17:24     ` Tom Tromey
2022-09-01 10:42 ` Andrew Burgess via Gdb-patches
2022-11-04 17:24   ` Simon Marchi via Gdb-patches
     [not found]     ` <8735asb7cj.fsf@redhat.com>
2022-11-09 13:19       ` Simon Marchi via Gdb-patches
2022-11-08 19:43 ` Pedro Alves
2022-11-08 20:14   ` Simon Marchi via Gdb-patches
2022-11-08 21:09     ` Pedro Alves
2022-11-08 21:20       ` [PATCH v2] " Simon Marchi via Gdb-patches
2022-11-10 16:45         ` Pedro Alves
2022-11-10 17:33           ` Simon Marchi via Gdb-patches
2022-11-10 17:36             ` Simon Marchi via Gdb-patches
2022-11-10 17:47             ` Pedro Alves
2022-11-10 17:53               ` Simon Marchi via Gdb-patches
2022-11-11 12:37         ` Tom de Vries via Gdb-patches
2022-11-11 13:53           ` Simon Marchi via Gdb-patches
2022-11-11 15:21             ` Tom de Vries via Gdb-patches
2022-11-11 19:03               ` Simon Marchi via Gdb-patches
2022-11-12 10:43                 ` Tom de Vries via Gdb-patches
2022-11-14 11:29                 ` Tom de Vries via Gdb-patches
2022-11-14 13:19                   ` Simon Marchi via Gdb-patches
2022-11-14 14:18                     ` Tom de Vries via Gdb-patches
2022-11-16 16:22                     ` Tom Tromey
2022-11-16 16:26                       ` Simon Marchi via Gdb-patches [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=cd5acab3-c67d-288e-8d13-69d75aa31abb@efficios.com \
    --to=gdb-patches@sourceware.org \
    --cc=simark@simark.ca \
    --cc=simon.marchi@efficios.com \
    --cc=tdevries@suse.de \
    --cc=tom@tromey.com \
    /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