From: Ben Elliston <bje@redhat.com>
To: Syd Polk <spolk@redhat.com>
Cc: sourcenav@sources.redhat.com
Subject: Re: Source navigator roadmap, features list, etc.?
Date: Thu, 28 Sep 2000 17:28:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.21.0009291127120.1719-100000@moshpit.cygnus.com> (raw)
In-Reply-To: <4.2.0.58.20000928132434.00cfe530@pop.cygnus.com>
We could certainly flag assignments of function pointers, but there is
no good static determination of when a function is actually called
dereferencing a function pointer. This requires runtime analysis. And
it could be wrong; the runtime analysis would have to have a reverse
table of addresses to functions. A debugger could do this while the
exe is running.
Or worse, the function pointer could be determined by address arithmetic.
As you say, there's only so much that can be done statically.
Ben
next prev parent reply other threads:[~2000-09-28 17:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-28 0:23 dave.banham
2000-09-28 13:25 ` Syd Polk
2000-09-28 17:28 ` Ben Elliston [this message]
2000-09-29 6:06 ` Bruce Stephens
-- strict thread matches above, loose matches on Subject: below --
2000-10-05 1:16 William Gacquer
2000-10-05 0:52 dave.banham
2000-10-04 0:53 leonp
2000-10-04 2:42 ` Timothy M. Shead
2000-09-29 0:26 dave.banham
2000-09-29 11:32 ` Syd Polk
[not found] <William>
[not found] ` <Gacquer's>
[not found] ` <message>
[not found] ` <of>
[not found] ` <"Wed,>
[not found] ` <27>
[not found] ` <Sep>
[not found] ` <2000>
[not found] ` <10:12:49>
[not found] ` <+0200>
2000-09-27 1:12 ` William Gacquer
2000-09-27 22:16 ` Bruce Stephens
2000-09-28 9:15 ` Berek
2000-09-28 13:26 ` Syd Polk
2000-09-28 13:22 ` Syd Polk
2000-10-03 16:02 ` Mo DeJong
2000-10-04 10:25 ` Syd Polk
2000-09-25 22:04 Timothee Besset
2000-09-26 9:23 ` Syd Polk
2000-09-26 10:30 ` Berek
2000-09-26 10:37 ` Syd Polk
2000-09-27 21:41 ` Ben Elliston
2000-10-03 9:44 ` Mo DeJong
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=Pine.LNX.4.21.0009291127120.1719-100000@moshpit.cygnus.com \
--to=bje@redhat.com \
--cc=sourcenav@sources.redhat.com \
--cc=spolk@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).