From: Mo DeJong <mdejong@cygnus.com>
To: sourcenav@sources.redhat.com
Subject: Re: Want Help with Source Navigator source code
Date: Mon, 30 Jul 2001 14:04:00 -0000 [thread overview]
Message-ID: <Pine.SOL.3.91.1010730140045.20099D-100000@cse.cygnus.com> (raw)
In-Reply-To: <146308CCF04B2E4DAD0C83898242D35A23D333@excsrv2.caemilusa.com>
On Mon, 30 Jul 2001, Salman Khilji wrote:
> I wanted some help with the source code of the Source Navigator. Usually,
> the developers and maintainers do not like to be sent direct e-mails. Their
> e-mail addresses are:
...
> If this is appropriate to ask, could you please forward this e-mail to them?
SN questions should be sent to the mailing list. Emails sent directly
to me often end up in the trash.
> NEED HELP WITH SOURCE CODE PARSING
> ==================================
>
> I am developing a debugger type application for C/C++/FORTRAN (not exactly a
> source line debugger). I need access to the complete symbol table of the
> target application.
It sounds like you want to hack GDB to do this sort of thing. SN is
more suited to static code analysis. SN is not a debugger so it does
not have access to some of the runtime info you might be interested in.
cheers
Mo
next prev parent reply other threads:[~2001-07-30 14:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-30 6:30 Salman Khilji
2001-07-30 14:04 ` Mo DeJong [this message]
2001-07-30 9:40 Syd Polk
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.SOL.3.91.1010730140045.20099D-100000@cse.cygnus.com \
--to=mdejong@cygnus.com \
--cc=sourcenav@sources.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).