public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jlarmour@redhat.com>
To: John Gumb <john@talisker.demon.co.uk>
Cc: "'ecos-discuss@sources.redhat.com'" <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] gdb 'next' problem with i386 HAL
Date: Thu, 16 Aug 2001 06:44:00 -0000	[thread overview]
Message-ID: <3B7BCE3A.92FDCA04@redhat.com> (raw)
In-Reply-To: <01C125FD.4894A7E0@bream.tr.localnet>

John Gumb wrote:
> 
> Hi,
> 
> I've managed to get the i386 HAL up and running without too much bother - the only oddity I have is with GDB. The 'step' command works fine but the 'next' command simply results in the program continuing without breaking at the next line.
> 
> I have seen some posts related to this in that the gdb front end translates 'next' into a setting of a temporary breakpoint and then issuing a 'continue' so I could imagine I might see this sort of behaviour.
> 
> After poking around a bit, I can't see anything obvious.

This works for me. What version of eCos/RedBoot? What version of GDB?

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine

  reply	other threads:[~2001-08-16  6:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-15 15:08 John Gumb
2001-08-16  6:44 ` Jonathan Larmour [this message]
2001-08-17  0:31   ` Boris V. Guzhov
2001-08-17  6:17     ` Jonathan Larmour
2001-08-22 12:20 Allan Young
2001-08-23  2:54 John Gumb
2001-08-24  7:19 Patrick O'Grady
2001-08-29  6:42 John Gumb
2001-08-29  6:47 ` Mark Salter
2001-09-05  8:32   ` Jonathan Larmour
2001-09-05  8:44     ` Mark Salter
2001-09-05  8:55       ` Jonathan Larmour
2001-09-05  9:33         ` Mark Salter
2001-09-05 14:16           ` Jonathan Larmour
2001-09-05 14:59             ` Mark Salter
2001-09-05 15:17               ` Jonathan Larmour

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=3B7BCE3A.92FDCA04@redhat.com \
    --to=jlarmour@redhat.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=john@talisker.demon.co.uk \
    /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).