From: Andrew Cagney <ac131313@cygnus.com>
To: Peter Barada <pbarada@mail.wm.sps.mot.com>
Cc: Peter.Barada@motorola.com, drow@mvista.com, gdb@sources.redhat.com
Subject: Re: Torubles with remote stub for m68k
Date: Tue, 25 Jun 2002 13:28:00 -0000 [thread overview]
Message-ID: <3D18D25F.6090203@cygnus.com> (raw)
In-Reply-To: <200206251638.g5PGcmI10826@hyper.wm.sps.mot.com>
>>> Ok, and what do I look for in the dump? I see:
>>>
>>> gdbarch_dump: MEMORY_INSERT_BREAKPOINT(addr, contents_cache) # (default_memory_insert_breakpoint (addr, contents_cache))
>>> gdbarch_dump: MEMORY_REMOVE_BREAKPOINT(addr, contents_cache) # (default_memory_remove_breakpoint (addr, contents_cache))
>>>
>>> But what else should I look for? I don't see anything that has 'step' in the name.
>
>>
>>SOFTWARE_SINGLE_STEP_P and SOFTWARE_SINGLE_STEP.
>>
>>Neither appear to be defined by the m68k targets. This indicates that
>>the m68k [in current gdb] does not support software single step.
>>
>
>
> What does that mean(the stub doesn't support single step?)?
The target doesn't support single step using software. However, I think
I've been barking up the wrong tree :-(
Andrew
next prev parent reply other threads:[~2002-06-25 20:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-24 12:46 [MI/testsuite] mi_gdb_test: expected result priority? Keith Seitz
2002-06-24 13:20 ` Elena Zannoni
2002-06-24 14:04 ` Torubles with remote stub for m68k Peter Barada
2002-06-24 14:13 ` Daniel Jacobowitz
2002-06-24 14:40 ` Peter Barada
2002-06-24 14:56 ` Peter Barada
2002-06-24 15:07 ` Daniel Jacobowitz
2002-06-24 15:30 ` Andrew Cagney
2002-06-24 15:35 ` Quality Quorum
2002-06-25 7:53 ` Peter Barada
2002-06-25 10:44 ` Andrew Cagney
2002-06-25 9:38 ` Peter Barada
2002-06-25 13:28 ` Andrew Cagney [this message]
2002-06-25 10:02 ` Daniel Jacobowitz
2002-06-25 8:13 ` Peter Barada
2002-06-25 8:17 ` Daniel Jacobowitz
2002-06-25 8:32 ` Peter Barada
2002-06-25 8:40 ` Daniel Jacobowitz
2002-06-25 13:43 ` Andrew Cagney
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=3D18D25F.6090203@cygnus.com \
--to=ac131313@cygnus.com \
--cc=Peter.Barada@motorola.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=pbarada@mail.wm.sps.mot.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).