public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Fernando Nasser <fnasser@cygnus.com>
To: Paul_Heijman@eu.omron.com
Cc: insight@sourceware.cygnus.com, fnasser@cygnus.com
Subject: Re: Insight Bug?
Date: Mon, 29 May 2000 08:12:00 -0000	[thread overview]
Message-ID: <39328879.62B27F10@cygnus.com> (raw)
In-Reply-To: <412568EE.004F2432.00@eu.omron.com>

Paul_Heijman@eu.omron.com wrote:
> 
> Hi folks,
> 
> I encountered the following, of what I think is a bug of Insight:
> 
> When I use the 'finish' button to complete a function, Insight apparently uses
> breakpoints for this (they are hidden someway).
> The problem is that when I press the 'continue' button afterwards, the 'hidden
> breakpoint' GDB used for the 'finish' function, is still there.
> Result: the program stops again.
> 
> I hope I explained the problem well enough for you, if I didn't, let me know.
> 

First of all: which host and which target are you talking about?
Which version of insight (gdb) are you using?  Where did you get it from?
How was it configured/compiled?  What is your O.S. version?

Te underlying debugger mechanism is very dependent on the architecture, OS
support and other details.  Problems may arise on a specific platform and not
on others.  Sometimes just in a specific OS version.  For remote targets,
sometimes is a problem with communication or withing a certain version of a
ROM monitor.

If you tell what your platform is, people with similar setups may be able to
help you with problems that the others may have no clue.


Another very important test one should do when encountering a problem while
using the GUI is to try running gdb with the command line interface.

Invoke gdb with "gdb -nw yourprog" (assuming you are debugging natively on a host)
and try the "finish" command at the same situation as above (try repeating the
corresponding actions you performed with the GUI).

This way we will know if it is a gdb problem or a GUI problem.  In you case, it must
be a gdb gdb probem as the GUI works fine on many systems.  If this is indeed the
case, please post your question to the gdb list as there may be people who have
seem your problem before or have some idea on how to investigate it further.  This is
the GUI list and people who sign to it are more into the user interface bits.

Regards.
F.


-- 
Fernando Nasser
Cygnus Solutions (a Red Hat company)    E-Mail:  fnasser@cygnus.com

  reply	other threads:[~2000-05-29  8:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-29  6:32 Paul_Heijman
2000-05-29  8:12 ` Fernando Nasser [this message]
2000-05-30  5:48 ` Finish [was: Insight Bug?] Fernando Nasser
2004-10-03  3:12 Insight Bug? Kip Warner
2004-10-03  3:43 ` Keith Seitz
     [not found] <opsfi9s0h3e8k94p@mail.thevertigo.com>
2004-10-08 14:29 ` Keith Seitz
     [not found]   ` <opsfn5rmzge8k94p@mail.thevertigo.com>
2004-10-10 19:40     ` 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=39328879.62B27F10@cygnus.com \
    --to=fnasser@cygnus.com \
    --cc=Paul_Heijman@eu.omron.com \
    --cc=insight@sourceware.cygnus.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).