public inbox for archer-commits@sourceware.org help / color / mirror / Atom feed
From: sergiodj@sourceware.org To: archer-commits@sourceware.org Subject: [SCM] archer-sergiodj-stap: Fixing problem when displacing a register's access with a positive number. Date: Tue, 15 Mar 2011 20:32:00 -0000 [thread overview] Message-ID: <20110315203209.1115.qmail@sourceware.org> (raw) The branch, archer-sergiodj-stap has been updated via e54d21757a87c22d7c3f0119ccc11aa1f4d0a4a4 (commit) from b7a8258a05fc4c3088b9b3f7e668400ca7fbb27a (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email. - Log ----------------------------------------------------------------- commit e54d21757a87c22d7c3f0119ccc11aa1f4d0a4a4 Author: Sergio Durigan Junior <sergiodj@redhat.com> Date: Tue Mar 15 17:31:01 2011 -0300 Fixing problem when displacing a register's access with a positive number. ----------------------------------------------------------------------- Summary of changes: gdb/stap-probe.c | 7 ++++++- 1 files changed, 6 insertions(+), 1 deletions(-) First 500 lines of diff: diff --git a/gdb/stap-probe.c b/gdb/stap-probe.c index da06db9..efa6018 100644 --- a/gdb/stap-probe.c +++ b/gdb/stap-probe.c @@ -781,7 +781,12 @@ stap_parse_single_operand (char **p, struct gdbarch *gdbarch, int number = strtol (s, &s, 0); if (!*s || !(*s == '(' && s[1] == '%')) - ; /* ERROR */ + error (_("Invalid register access on expression `%s'."), + stap_saved_expression); + + res + = value_from_longest (builtin_type (gdbarch)->builtin_int, + number); res = stap_fetch_reg_value (&s, gdbarch, bitness, frame, res); hooks/post-receive -- Repository for Project Archer.
reply other threads:[~2011-03-15 20:32 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20110315203209.1115.qmail@sourceware.org \ --to=sergiodj@sourceware.org \ --cc=archer-commits@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: linkBe 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).