From: Dave Lawrence <dlawrence@ad-holdings.co.uk>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] Re: GDB stops randomly
Date: Wed, 21 Feb 2007 07:45:00 -0000 [thread overview]
Message-ID: <erfeae$bbh$1@sea.gmane.org> (raw)
In-Reply-To: <1170683150.7106.6.camel@localhost>
I have also seen this with Insight, and annoyingly the GUI doesn't
always indicate the presence of these breakpoints. If you delete
gdbtk.ini (or less drastic, edit it) the problem goes away, at least, it
goes away for the current build of code, if you add more breakpoints,
then the problem will come back for a future build...
Donald Walton wrote:
> I have noticed this behavior when I use Insight. The cause was editing
> the program in the area where a breakpoint had been set. The editing
> process can leave the previously set breakpoint invalid.
>
> If you have breakpoints set when you go into your program, check them
> before you run the program to verify they are still valid, i.e., on a
> line of code.
>
> Don
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2007-02-21 7:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-05 11:14 [ECOS] " Carlos Losada
2007-02-05 11:43 ` Andrew Lunn
2007-02-05 13:45 ` Donald Walton
2007-02-21 7:45 ` Dave Lawrence [this message]
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='erfeae$bbh$1@sea.gmane.org' \
--to=dlawrence@ad-holdings.co.uk \
--cc=ecos-discuss@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).