Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Simon Marchi <simon.marchi@efficios.com>
Cc: Tom Tromey <tom@tromey.com>,
	 Simon Marchi <simon.marchi@polymtl.ca>,
	 gdb-patches@sourceware.org
Subject: Re: [PATCH] Use -qualified flag when setting temporary breakpoint in start command
Date: Thu, 25 Apr 2019 15:52:00 -0000	[thread overview]
Message-ID: <87v9z2axqt.fsf@tromey.com> (raw)
In-Reply-To: <96f5e735-0cdd-8bcb-58cf-e3986a5e3d5d@efficios.com> (Simon	Marchi's message of "Thu, 25 Apr 2019 11:31:59 -0400")

>>>>> "Simon" == Simon Marchi <simon.marchi@efficios.com> writes:

Simon> I presume there is no Ada or Rust test that specifically check the situation
Simon> where a non-qualified breakpoint on "main" (or equivalent for the language) would
Simon> result in a multi-location breakpoint.

Probably not.  I think my main concern is just that it continues to work
when the name of "main" is something that already has qualifiers.

Simon> Can you help by providing Ada and Rust snippets that would result in multi-location
Simon> breakpoints on main (or whatever the entry point is called)?  I could then convert
Simon> them to test cases.

I think actually my worry would be addressed by any "start" test in
those languages, because the main to stop at is always qualified.

Tom


      parent reply	other threads:[~2019-04-25 15:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-09  2:56 Simon Marchi
2019-04-09 15:27 ` Pedro Alves
2019-04-09 16:19   ` Simon Marchi
2019-04-09 16:30     ` Pedro Alves
2019-04-09 16:37       ` Simon Marchi
2019-04-09 18:09 ` André Pönitz
2019-04-09 22:02   ` [PP?] " Simon Marchi
2019-04-10 18:22     ` André Pönitz
2019-04-25 14:10 ` Tom Tromey
     [not found]   ` <96f5e735-0cdd-8bcb-58cf-e3986a5e3d5d@efficios.com>
2019-04-25 15:52     ` Tom Tromey [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=87v9z2axqt.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@efficios.com \
    --cc=simon.marchi@polymtl.ca \
    /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