public inbox for
help / color / mirror / Atom feed
Subject: insight/273: bad behaviour od STEP, NEXT buttons, empty for() loop crashes
Date: Wed, 21 Sep 2005 13:23:00 -0000	[thread overview]
Message-ID: <> (raw)

>Number:         273
>Category:       insight
>Synopsis:       bad behaviour od STEP, NEXT buttons, empty for() loop crashes
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Sep 21 13:23:01 UTC 2005
>Originator:     vaclav peroutka
>Release:        insight/gdb 6.0
winXP, cygwin, arm-elf distribution got from
When running delay loop with empty for() cycle:
    for (i=0; i<0x3ffff; i++);
STEP or NEXT button will freeze the communication with the board through wiggler.

If I use following loop:
    i = 0;
    while (i < 0xfffff) {
or put something in brackets in for() loop it works ok. But STEP button has the same behaviour as NEXT button. It should "skip" the loop, shouldn't it?

If I am inside the loop pressing the FINISH button runs program without finishing just the loop. But it continues further.
1. connect Wiggler to parallel port and the target board
2. run ocdremote.exe
3. run arm-elf-insight
4. open the elf program with for() loop
5. connect to Remote/TCP localhost:8888
6. download the program
7. set breakpoint in front of for() loop
8. run
9. step
10. now it is not possible to stop it

similarly it is possible to test behaviour of STEP/NEXT/FINISH buttons

I don't attach C source code because it is processor dependant. But anybody can use the simplest flash LED code.


                 reply	other threads:[~2005-09-21 13:23 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).