From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
gdb-patches@sourceware.org,
Jan Kratochvil <jan.kratochvil@redhat.com>,
Pedro Alves <palves@redhat.com>
Subject: Re: [commit] Improved linker-debugger interface
Date: Wed, 26 Jun 2013 17:23:00 -0000 [thread overview]
Message-ID: <m37ghgx0dv.fsf@redhat.com> (raw)
In-Reply-To: <87hagkrih3.fsf@fleche.redhat.com> (Tom Tromey's message of "Wed, 26 Jun 2013 09:37:28 -0600")
On Wednesday, June 26 2013, Tom Tromey wrote:
> It seems to me that we could make the warning more verbose and have it
> request that users file a bug report; and it could include a little
> explanation, plus some text to report. Like:
>
> warning: Probes-based dynamic linker interface failed:
> Unknown numeric token ...
> This means there is a bug, either in gdb or elsewhere in the
> toolchain. Please report it to the gdb bugzilla, along with
> this information:
> Arch: Whatever
> Probe name: ...
> Argument number: ...
> Argument text: ...
>
> Being extra wordy is a bit of a pain, maybe, since presumably users will
> see it often. OTOH, it's a "shouldn't happen" scenario where gdb has
> lots of information already...
Sounds good to me, but...
> Also, I wonder why we're trying to use the probes on a platform to which
> the gdb side hasn't been ported. Are we just optimistically trying to
> parse the assembly operands here?
That's a relevant question. GDB has a generic asm parser (implemented
in stap-probe.c), which makes use of specific target-dep
functions/variables to correctly handle the idiosyncrasies of each type
of asm.
So far, we have support for x86, x86_64, PPC, PPC64, ARM, and a pending
patch for IA-64. However, there must be more architectures where we
will need to implement it. The pre-requisite I am/was using is: if
systemtap-sdt-devel is installable on the system, then GDB needs to
support SDT probes. Unfortunately I failed to check IA-64, but that is
hopefully fixed now.
OTOH, if the user successfuly installs <sys/sdt.h> on her system, then
GDB should at least be prepared to avoid trying to parse something it
doesn't fully understand.
What could be done is to check gdbarch_stap_is_single_operand_p. This
is a mandatory function that needs to be set by the target. If it
doesn't exist, then we know that the target lacks SDT support.
Before I work on a patch, I'd like to know what you think.
Thanks,
--
Sergio
next prev parent reply other threads:[~2013-06-26 17:11 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-16 14:43 [RFA 0/7] " Gary Benson
2013-05-16 14:47 ` [RFA 1/7] Probes API convenience patch Gary Benson
2013-05-16 14:48 ` [RFA 4/7] GDB support for new gdbserver functionality Gary Benson
2013-05-16 14:48 ` [RFA 2/7] API for inhibiting section map updates Gary Benson
2013-05-20 14:22 ` Tom Tromey
2013-05-24 7:47 ` [RFA 2/7 take 2] " Gary Benson
2013-05-24 14:18 ` Tom Tromey
2013-05-29 17:18 ` Pedro Alves
2013-05-30 9:12 ` Gary Benson
2013-05-16 14:48 ` [RFA 3/7] New gdbserver functionality Gary Benson
2013-05-16 18:18 ` Tom Tromey
2013-05-24 7:46 ` [RFA 3/7 take 2] " Gary Benson
2013-05-25 21:05 ` Jan Kratochvil
2013-05-26 2:45 ` Eli Zaretskii
2013-05-29 18:50 ` Pedro Alves
2013-05-30 9:38 ` Gary Benson
2013-05-30 10:40 ` Pedro Alves
2013-05-30 10:54 ` Gary Benson
2013-05-30 16:31 ` Eli Zaretskii
2013-05-30 17:22 ` Gary Benson
2013-05-16 14:55 ` [RFA 7/7] Linker-debugger interface tests Gary Benson
2013-05-19 13:45 ` Jan Kratochvil
2013-05-19 16:43 ` Jan Kratochvil
2013-05-24 8:38 ` [RFA 7/7 take 2] " Gary Benson
2013-05-24 8:58 ` Jan Kratochvil
2013-05-24 14:05 ` [obv] Fix excessive backslashes in testsuite Gary Benson
2013-05-25 21:06 ` [RFA 7/7 take 2] Linker-debugger interface tests Jan Kratochvil
2013-05-16 14:55 ` [RFA 6/7] Linker-debugger interface tests by Jan Gary Benson
2013-05-29 19:06 ` Pedro Alves
2013-05-30 9:19 ` Gary Benson
2013-05-16 14:55 ` [RFA 5/7] Improved linker-debugger interface Gary Benson
2013-05-17 19:05 ` Jan Kratochvil
2013-05-24 8:30 ` [RFA 5/7 take 2] " Gary Benson
2013-05-25 21:05 ` Jan Kratochvil
2013-05-29 18:51 ` Pedro Alves
2013-05-30 10:43 ` [RFA 5/7 take 3] " Gary Benson
2013-05-30 17:18 ` Pedro Alves
2013-05-31 13:22 ` [RFA 5/7 take 4] " Gary Benson
2013-05-31 13:27 ` Pedro Alves
2013-06-03 10:31 ` Pedro Alves
2013-06-03 16:37 ` Jan Kratochvil
2013-06-03 17:28 ` Pedro Alves
2013-06-04 11:33 ` Gary Benson
2013-05-16 17:33 ` [RFA 0/7] " Tom Tromey
2013-05-16 18:53 ` Gary Benson
2013-06-06 9:00 ` Gary Benson
2013-05-19 13:46 ` Jan Kratochvil
2013-05-29 19:08 ` Pedro Alves
2013-06-04 13:38 ` [commit] " Gary Benson
2013-06-25 21:04 ` Joel Brobecker
2013-06-25 22:03 ` Sergio Durigan Junior
2013-06-26 0:49 ` Joel Brobecker
2013-07-09 8:41 ` Gary Benson
[not found] ` <20130708104719.GA11176@blade.nx>
2013-07-09 14:45 ` Joel Brobecker
2013-06-26 15:38 ` Tom Tromey
2013-06-26 17:23 ` Sergio Durigan Junior [this message]
2013-06-26 19:15 ` Joel Brobecker
2013-06-27 23:33 ` Tom Tromey
2013-06-30 3:12 ` Sergio Durigan Junior
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=m37ghgx0dv.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=palves@redhat.com \
--cc=tromey@redhat.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