From: "Zaric, Zoran \(Zare\) via Gdb-patches" <gdb-patches@sourceware.org>
To: Tom Tromey <tom@tromey.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH v2] Replace the symbol needs evaluator with a parser
Date: Mon, 30 Nov 2020 18:18:34 +0000 [thread overview]
Message-ID: <DM6PR12MB27628557A57F87E126B39802F8F50@DM6PR12MB2762.namprd12.prod.outlook.com> (raw)
In-Reply-To: <DM6PR12MB27625E6584A0912609CE96C3F8E70@DM6PR12MB2762.namprd12.prod.outlook.com>
[AMD Official Use Only - Internal Distribution Only]
> Sorry Tom, I didn't get what you were aiming at by the 1 and 2. To late for
> me I guess.
>
> And yes, my scanner would have a problem if somebody used DWARF like
> that, and it would behave differently then the evaluator, but the previous
> evaluation (without accessing the target) would hit many the same issues as
> well. The only issue that it wouldn't probably hit is if the absolute jump
> would jump over the garbage.
Tom, following on our last discussion, are you OK with the changes going in as they are?
We can always think about using a new evaluator design that throws exceptions to reimplement this in a later stage.
This could be a straightforward thing to do if my next patch series seems interesting to the community.
Zoran
prev parent reply other threads:[~2020-11-30 18:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 17:26 Zoran Zaric
2020-10-21 20:35 ` Tom Tromey
2020-10-22 14:58 ` Zaric, Zoran (Zare)
2020-10-27 19:51 ` Pedro Alves
2020-11-12 20:03 ` Tom Tromey
2020-11-12 20:11 ` Tom Tromey
2020-11-12 21:17 ` Zaric, Zoran (Zare)
2020-11-12 21:29 ` Zaric, Zoran (Zare)
2020-11-30 18:18 ` Zaric, Zoran (Zare) via Gdb-patches [this message]
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=DM6PR12MB27628557A57F87E126B39802F8F50@DM6PR12MB2762.namprd12.prod.outlook.com \
--to=gdb-patches@sourceware.org \
--cc=Zoran.Zaric@amd.com \
--cc=tom@tromey.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