public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jlarmour@redhat.com>
To: "Boris V. Guzhov" <borg@int.spb.ru>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] gdb 'next' problem with i386 HAL
Date: Fri, 17 Aug 2001 06:17:00 -0000	[thread overview]
Message-ID: <3B7D198D.89110FA1@redhat.com> (raw)
In-Reply-To: <000901c126ed$1c29f160$7601a8c0@int.spb.ru>

"Boris V. Guzhov" wrote:
> 
> Hi,
> I also have such behaviour of the debugger.
> My host Linux Redhat 6.2.
> gdb version: i386-elf-gdb --verison returns GDB 5.0.
> eCos version (with Redboot)  from anon CVS  (Juli 25)

Okay, I don't know why that shouldn't work - certainly I was debugging on
the PC target from the anon cvs code just last week.

Perhaps it might behave better if the debugged app was built with no
optimization. Other than that, you'll need to investigate further (e.g. by
using "set debug remote 1" and seeing where GDB sets its "next" breakpoint
and see if that's valid).

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-17  6:17 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
2001-08-17  0:31   ` Boris V. Guzhov
2001-08-17  6:17     ` Jonathan Larmour [this message]
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=3B7D198D.89110FA1@redhat.com \
    --to=jlarmour@redhat.com \
    --cc=borg@int.spb.ru \
    --cc=ecos-discuss@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).