public inbox for insight-prs@sourceware.org
help / color / mirror / Atom feed
From: kseitz@sources.redhat.com
To: insight-prs@sources.redhat.com, kseitz@sources.redhat.com,
	nobody@sources.redhat.com, pal.frenger@ericsson.com
Subject: Re: insight/235: "Step" and "Next" doesn't work. Instead I get "Step Asm Inst" and "Next Asm Inst"
Date: Wed, 20 Aug 2003 14:55:00 -0000	[thread overview]
Message-ID: <20030820145508.19208.qmail@sources.redhat.com> (raw)

Synopsis: "Step" and "Next" doesn't work. Instead I get "Step Asm Inst" and "Next Asm Inst"

Responsible-Changed-From-To: unassigned->kseitz
Responsible-Changed-By: kseitz
Responsible-Changed-When: Wed Aug 20 14:55:08 2003
Responsible-Changed-Why:
    mine
State-Changed-From-To: open->analyzed
State-Changed-By: kseitz
State-Changed-When: Wed Aug 20 14:55:08 2003
State-Changed-Why:
    Your bug report is a little sparse on information, but let me explain what is supposed to happen.
    
    When debugging in SOURCE mode, you should step in the source language (i.e. N does "next" for C/C++/Java/etc; "nexti" for assembly).
    
    When debugging in MIXED mode or ASSEMBLY mode, N does "nexti" and S does "stepi".
    
    When debugging in SRC+ASM mode, N will do "next" if the mouse is in the SRC pane; "nexti" if it is in the ASM pane.
    
    So, if the source window is displaying assembly, the only way to single-step one source line is to press the next button on the toolbar or select it from the menu.
    
    Have you tried 6.0?

http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=insight&pr=235


             reply	other threads:[~2003-08-20 14:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-20 14:55 kseitz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-09-16 18:43 iainmelvin
2003-08-05 16:43 pal.frenger

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=20030820145508.19208.qmail@sources.redhat.com \
    --to=kseitz@sources.redhat.com \
    --cc=insight-gnats@sources.redhat.com \
    --cc=insight-prs@sources.redhat.com \
    --cc=nobody@sources.redhat.com \
    --cc=pal.frenger@ericsson.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).