From: "Frank Ch. Eigler" <fche@redhat.com>
To: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
Cc: elfutils-devel@sourceware.org
Subject: Re: eu-dbgserver vs. valgrind --debuginfo-server=ipaddr:port
Date: Fri, 20 Sep 2019 14:28:00 -0000 [thread overview]
Message-ID: <20190920142830.GC31972@redhat.com> (raw)
In-Reply-To: <201909200342.x8K3gxYD012293@ignucius.se.axis.com>
Hi, HP -
> Hi. I attended FChE's debuginfo-server talk at the GNU Tools
> Cauldron (nice meeting you there BTW).
Yes, lovely!
> I happened to re-read the valgrind manpage yesterday (grr:
> --error-exitcode isn't the default) and stumbled upon a "new"
> feature mentioned there: apparently valgrind has a debug-info
> server of its own, for use with its
> --debuginfo-server=ipaddr:port option (in version 3.9.0+).
Heh, I wasn't actually aware of this one, thanks! Yeah, they're not
compatible or identical in scope, only in inspiration in the problem
space (debug data may be somewhere else). The buildid-based search
elsewhere in valgrind (find_debug_file()) would be a good place to add
the new quiet call. If that fails, the old client/server
filename-based logic could still be retained as a fallback.
> (Patches to support valgrind queries you say? Sorry, can't
> volunteer until I'm done with all my other chores to do more
> than this cursory investigation. :)
:-)
- FChE
next prev parent reply other threads:[~2019-09-20 14:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 3:43 Hans-Peter Nilsson
2019-09-20 14:28 ` Frank Ch. Eigler [this message]
2019-09-20 14:39 ` Hans-Peter Nilsson
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=20190920142830.GC31972@redhat.com \
--to=fche@redhat.com \
--cc=elfutils-devel@sourceware.org \
--cc=hans-peter.nilsson@axis.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).