From: Syd Polk <spolk@baritoneconsulting.com>
To: Bruce Edson <bruce@steptech.com>
Cc: "Sourcenav (E-mail)" <sourcenav@sources.redhat.com>
Subject: Re: Debugging under Windows environment
Date: Tue, 05 Mar 2002 12:06:00 -0000 [thread overview]
Message-ID: <E226AC8D-3073-11D6-971C-000A27917828@baritoneconsulting.com> (raw)
In-Reply-To: <26F9F6EAB586D411850700B0D049E6E4014D2E9E@shasta.pdx.steptech.com>
On Tuesday, March 5, 2002, at 10:53 , Bruce Edson wrote:
> I have successfully built Source Navigator on Windows 2000 under the
> Cygwin
> bash shell. I am now in the process of making
> modifications/enhancements to
> the application. I now need to embark on debugging changes and have
> some
> questions.
I assume you used the Microsoft compiler.
>
> 1. What is the best way to go about debugging the application, and/or my
> changes?
>
> 2. Do I debug from within Cygwin, or Windows?
>
Since you have used the Microsoft compiler, using the Visual Studio
debugger is the correct way.
However, unless you are in the C code, I would use the hyper console
interactively to debug your tcl code.
> 3. What tool is best to use, and does it have the typical debug
> capabilities? (assuming I can't use MS VC++ Visual Studio)
>
You managed to get it up and running compiling with gcc? Then, use gdb.
> 4. How do I build a debuggable version of the application?
>
If you used Visual Studio, I believe you need to set CFLAGS to "-Z7" or
some such when configuring. If you used gcc, "-g".
> 5. Where is there documentation about debugging in this environment?
>
Well, there isn't much.
> Thanks in advance!
>
> Bruce Edson
> bruce@steptech.com
>
>
next prev parent reply other threads:[~2002-03-05 20:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-05 12:02 Bruce Edson
2002-03-05 12:06 ` Syd Polk [this message]
2002-03-05 12:02 Left Spin
2002-03-05 12:57 Left Spin
2002-03-05 17:45 ` 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=E226AC8D-3073-11D6-971C-000A27917828@baritoneconsulting.com \
--to=spolk@baritoneconsulting.com \
--cc=bruce@steptech.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).