From: Daniel Jacobowitz <drow@false.org>
To: Pedro Alves <pedro_alves@portugalmail.pt>
Cc: gdb@sourceware.org, personel personel <lepascal01@yahoo.com>,
gdb-patches <gdb-patches@sourceware.org>
Subject: Re: Debugging a Vlc dll with GDB.
Date: Fri, 07 Dec 2007 00:42:00 -0000 [thread overview]
Message-ID: <20071207004226.GA30430@caradoc.them.org> (raw)
In-Reply-To: <475893BA.8000700@portugalmail.pt>
On Fri, Dec 07, 2007 at 12:28:42AM +0000, Pedro Alves wrote:
> I could swear there use to be a "pending resolved"
> notice. Did it go away with the multiple breakpoint
> location support?
Yes, I believe so. It was mostly there to warn you that the
breakpoint number had changed, which Vladimir has now fixed.
> if (pending_break_support == AUTO_BOOLEAN_AUTO &&
> - !nquery ("Make breakpoint pending on future shared library load? "))
> + !nquery (_("\
> +Make breakpoint pending on future symbol file addition? ")))
Accurate, but I don't like it much... sounds awkward.
For the rest, I don't really like the churn on messages; would it work
to just push the error down below *not_found_ptr = 1, and make it a
NOT_FOUND_ERROR?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-12-07 0:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-06 17:38 personel personel
2007-12-06 17:53 ` Dave Korn
2007-12-06 18:23 ` Daniel Jacobowitz
2007-12-06 20:15 ` personel personel
2007-12-06 20:29 ` Daniel Jacobowitz
2007-12-06 20:57 ` Brian Dessent
2007-12-07 0:28 ` Pedro Alves
2007-12-07 0:42 ` Daniel Jacobowitz [this message]
2007-12-07 1:57 ` Pedro Alves
2007-12-07 13:54 ` Daniel Jacobowitz
2007-12-08 10:54 ` Eli Zaretskii
2007-12-07 16:21 ` Dave Korn
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=20071207004226.GA30430@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=gdb@sourceware.org \
--cc=lepascal01@yahoo.com \
--cc=pedro_alves@portugalmail.pt \
/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).