public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
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:21:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.33.0110231518060.23825-100000@makita.cygnus.com> (raw)
In-Reply-To: <3BD5EEC0.3F64D86B@redhat.com>

On Tue, 23 Oct 2001, Ian Roxborough wrote:

> > 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?
>
> Both show the same as the breakpoint window (i.e. the breakpoints set
> in the wrong places).

My initial reaction to this is "it's not possible". Entering "break
foo.c:124" is the same whether or not its done at the command line or at
the console prompt. The only difference is that when Insight is around, an
event is sent to the gui.

I would expect to see problems with the Func Browser or the SrcWin, since
these use different mechanisms for setting breakpoints than the console
window.

Something really weird is going on, and I guess the only way to resolve it
is to debug it. I will see if I can get to it tonight.

Keith


  reply	other threads:[~2001-10-23 15:21 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   ` FYI: DLL breakpoint bug [was: Re: DLLs and Insight...] Ian Roxborough
2001-10-23 14:36     ` 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 [this message]
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=Pine.GSO.4.33.0110231518060.23825-100000@makita.cygnus.com \
    --to=keiths@cygnus.com \
    --cc=insight@sources.redhat.com \
    --cc=irox@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).