From: Ian Roxborough <irox@redhat.com>
To: egcs@cygnus.com
Cc: insight@sources.redhat.com
Subject: FYI: DLL breakpoint bug [was: Re: DLLs and Insight...]
Date: Tue, 23 Oct 2001 14:30:00 -0000 [thread overview]
Message-ID: <3BD5E45C.C8F43F71@redhat.com> (raw)
In-Reply-To: <Pine.GSO.4.33.0110231023460.23825-100000@makita.cygnus.com>
Hi,
well, I deleted my build tree, did a clean build and
was able to see sources/debug symbols from DLLs in Insight.
I probably had it working but didn't actually start the
application to load the symbol info into Insight first
time around. Thanks for all the pointers and help.
And soon after that I found a breakpoint related bug.
If I try to set a breakpoint in a DLL using the Function Browser
(actually, even if I set it in the console) it sets the
breakpoint at the same line but in some other file (which
was loaded at start up). This seems related to the Tcl/Tk
upgrade since I tried it with a version of Insight built
using Tcl/Tk8.0 and wasn't able to reproduce the problem.
Ian.
next prev parent reply other threads:[~2001-10-23 14:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-23 10:20 DLLs and Insight Ian Roxborough
2001-10-23 10:27 ` Keith Seitz
2001-10-23 14:30 ` Ian Roxborough [this message]
2001-10-23 14:36 ` FYI: DLL breakpoint bug [was: Re: DLLs and Insight...] Keith Seitz
2001-10-23 14:59 ` Ian Roxborough
2001-10-23 15:05 ` Keith Seitz
2001-10-23 15:14 ` Ian Roxborough
2001-10-23 15:21 ` Keith Seitz
2001-10-23 15:33 ` Ian Roxborough
2001-10-24 13:33 ` Keith Seitz
2001-10-23 10:52 ` DLLs and Insight Fernando Nasser
2001-10-23 11:06 ` Christopher Faylor
2001-10-31 9:24 ` Stack Window Problem [was: Re: DLLs and Insight...] Ian Roxborough
2001-10-31 10:48 ` Fernando Nasser
2001-10-31 11:33 ` Ian Roxborough
2001-10-31 11:53 ` Christopher Faylor
2001-11-01 11:42 ` Fernando Nasser
2001-11-01 12:44 ` Ian Roxborough
2001-11-01 12:48 ` Keith Seitz
2001-11-01 13:01 ` Christopher Faylor
2001-11-01 13:20 ` Ian Roxborough
2001-11-01 14:05 ` Keith Seitz
2001-11-01 15:08 ` Christopher Faylor
2001-11-01 15:41 ` Keith Seitz
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=3BD5E45C.C8F43F71@redhat.com \
--to=irox@redhat.com \
--cc=egcs@cygnus.com \
--cc=insight@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).