From: Robert Dewar <dewar@adacore.com>
To: Francois Chouinard <fchouinard@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Problem setting a breakpoint at a location containing spaces (using MI)
Date: Thu, 12 Feb 2009 19:09:00 -0000 [thread overview]
Message-ID: <499473D7.9020603@adacore.com> (raw)
In-Reply-To: <578d90ee0902121102h75129e60xec5aae8a15820b08@mail.gmail.com>
Francois Chouinard wrote:
> Hi,
>
> I know this sounds supremely basic but, using MI, what would be the
> syntax to insert a breakpoint when specifying a location containing
> spaces?
It always surprises me that people would cause themselves grief
by putting spaces into source file names (or the directories
where they live). This is asking for trouble with tools.
next prev parent reply other threads:[~2009-02-12 19:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 19:02 Francois Chouinard
2009-02-12 19:09 ` Robert Dewar [this message]
[not found] ` <578d90ee0902121323s30299358y326cb7776ec7f3be@mail.gmail.com>
2009-02-12 21:33 ` Francois Chouinard
2009-02-12 21:49 ` Francois Chouinard
2009-02-12 22:43 ` Tom Tromey
2009-02-12 22:50 ` Francois Chouinard
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=499473D7.9020603@adacore.com \
--to=dewar@adacore.com \
--cc=fchouinard@gmail.com \
--cc=gdb@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