From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@suse.de>
Cc: andrew.stubbs@st.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] Don't give spurious warnings when using thread specific breakpoints
Date: Thu, 19 Oct 2006 04:17:00 -0000 [thread overview]
Message-ID: <uirihq6qr.fsf@gnu.org> (raw)
In-Reply-To: <jed58pcr53.fsf@sykes.suse.de> (message from Andreas Schwab on Wed, 18 Oct 2006 22:20:40 +0200)
> From: Andreas Schwab <schwab@suse.de>
> Cc: Andrew STUBBS <andrew.stubbs@st.com>, gdb-patches@sourceware.org
> Date: Wed, 18 Oct 2006 22:20:40 +0200
> >
> > ALL_BREAKPOINTS (b)
> > if (b->loc->address == pc) /* address match / overlay match */
> > if (!b->pending && (!overlay_debugging || b->loc->section == section))
> > {
> > others--;
> > if (others == 1 &&
> > (b->enable_state == bp_disabled ||
> > b->enable_state == bp_shlib_disabled ||
> > b->enable_state == bp_call_disabled))
> > printf_filtered (_("Note: breakpoint %d (disabled) also set at pc "),
>
> That won't work either. Some languages (notably German) need to put the
> verb at the end of the sentence in such a case.
Yes, for better results the following call to
deprecated_print_address_numeric should be made a part of the message
(as a format specifier, for example, or concatenated string).
next prev parent reply other threads:[~2006-10-19 4:17 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 13:44 Andrew STUBBS
2006-10-11 13:55 ` Daniel Jacobowitz
2006-10-11 14:46 ` Andrew STUBBS
2006-10-11 20:45 ` Daniel Jacobowitz
2006-10-11 22:12 ` Mark Kettenis
2006-10-11 22:14 ` Joel Brobecker
2006-10-18 12:01 ` Andrew STUBBS
2006-10-18 14:14 ` Daniel Jacobowitz
2006-10-18 15:12 ` Andrew STUBBS
2006-10-18 19:47 ` Eli Zaretskii
2006-10-18 20:21 ` Andreas Schwab
2006-10-19 4:17 ` Eli Zaretskii [this message]
2006-10-19 9:47 ` Andrew STUBBS
2006-10-20 6:10 ` Eli Zaretskii
2006-10-20 14:29 ` Daniel Jacobowitz
2006-10-20 17:42 ` Eli Zaretskii
2006-10-20 17:47 ` Daniel Jacobowitz
2006-10-20 18:03 ` Eli Zaretskii
2006-10-20 18:07 ` Daniel Jacobowitz
2006-10-20 18:11 ` Eli Zaretskii
2006-10-19 13:28 ` Daniel Jacobowitz
2006-10-19 15:59 ` Andrew STUBBS
2006-10-18 19:22 ` Eli Zaretskii
2006-10-11 22:06 ` Mark Kettenis
2006-10-12 10:45 ` Andrew STUBBS
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=uirihq6qr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=andrew.stubbs@st.com \
--cc=gdb-patches@sourceware.org \
--cc=schwab@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