From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keith Seitz <keiths@cygnus.com>
To: Ian Roxborough <irox@redhat.com>
Cc: <insight@sources.redhat.com>
Subject: Re: FYI: DLL breakpoint bug [was: Re: DLLs and Insight...]
Date: Tue, 23 Oct 2001 15:05:00 -0000
Message-id: <Pine.GSO.4.33.0110231503580.23825-100000@makita.cygnus.com>
References: <3BD5EB1C.45CC6233@redhat.com>
X-SW-Source: 2001-q4/msg00176.html

On Tue, 23 Oct 2001, Ian Roxborough wrote:

> It works with "gdb -nw".

Joy. This means that the command-line does some magic that our breakpoint
interfaces don't handle.

> If in the console I type "break tkWinWm.c:4203" it replies that the breakpoint
> is set at that location.  But if I look at the breakpoints window it lists
> the breakpoint as being set in tclCompile.c at line 4203.  If I use the
> Function Browser to set the same breakpoint it sets it in tclCompile.c at
> line 1109.

This is odd. I would not expect entering the breakpoint at the console
prompt to change the breakpoint. Does "info break" show the right
location? What does "tk gdb_get_breakpoint_info BKPT#" show?

Keith