Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Quality Quorum <qqi@theworld.com>
To: Squal <pmarty@enssat.fr>
Cc: gdb@sources.redhat.com
Subject: Re: remote debugging with m68k-stub
Date: Wed, 07 Aug 2002 07:22:00 -0000	[thread overview]
Message-ID: <Pine.SGI.4.40.0208071012320.71667382-100000@shell01.TheWorld.com> (raw)
In-Reply-To: <3D511895.F61D82A1@enssat.fr>



On Wed, 7 Aug 2002, Squal wrote:

> Hello!
>
> I have done all the remote target gdb instructions:
>   - define all the low level routines
>   - insert set_debug_traps(); and breakpoints(); at
>     the beginning of the program
>   - compiling stub and program together
>
> After that, I downloaded my program and the m68k-stub in the target.
> My problem is when I start the program in the remote target, the program
> stop and never restart (the halt indicator is set).
> Normally, the program will stop at the breakpoint (TRAP #1) and will
> continue after gdb be connected to the stub but the program seems to
> be stopped.

If you this is not the first time you are running gdb in this environment
check changes you made. If it is the first time it is quite possible that
you have conflict between you ROM monitor (I suspect this is what you call
target) initialization and gdb initialization.
>
> Somebody can help me ?

1. Use ICE if it is available

or


2. Trace the thing with characters sent to serial port.


>
> Thanks
>
> Pascal
>

There are simply no smart ways to debug initialization, also do not forget
to read you target doc, it is quite possible that they have some
debugging help.

Thanks,

Aleksey



  reply	other threads:[~2002-08-07 14:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-07  5:49 Squal
2002-08-07  7:22 ` Quality Quorum [this message]
2002-08-07  8:17 ` William A. Gatliff
2002-08-14  2:34 Squal

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=Pine.SGI.4.40.0208071012320.71667382-100000@shell01.TheWorld.com \
    --to=qqi@theworld.com \
    --cc=gdb@sources.redhat.com \
    --cc=pmarty@enssat.fr \
    /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