From: "Xavier Wang" <xavierwang@ms19.url.com.tw>
To: <ecos-discuss@sources.redhat.com>
Subject: [ECOS] GDB Ctrl-C problem
Date: Tue, 27 Feb 2001 23:00:00 -0000 [thread overview]
Message-ID: <004f01c0a152$d298e6c0$1c2414ac@realtek.com.tw> (raw)
Hi,
I'm porting eCos to a MIPS architecture from TX39/JMR3904
template. My problem is that when I press Ctrl-C in GDB,
the program stops at breakpoint() (in hal_stub.c) which contains
only one instruction: HAL_BREAKPOINT(_breakinst). How
could I let the GDB stop exactly at the interrupted instruction
rather than the breakpoint instruction itself? By looking into
cyg_hal_user_break(), it seems that it might help if
CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS is defined,
since in that case it will call breakpoint() instead of calling
HAL_BREAKPOINT() directly, and it seems that breakpoint()
should handle the program counter stuff. But in fact the breakpoint()
contains only one instruction HAL_BREAKPOINT(), so it makes
no difference. Could cyg_hal_gdb_interrupt() help? Can I replace
breakpoint() with cyg_hal_gdb_interrupt() in cyg_hal_user_break()?
The following is my configurations:
- eCos v1.3.1
- GDB stubs
GDB Ctrl-C support enabled
GDB break support disabled
Startup type = ROM
loaded and run by ICE
- application
GDB stubs included
GDB Ctrl-C support enabled
GDB break support disabled
Work with a ROM Monitor = GDB stubs
Startup type = RAM
Thank you.
next reply other threads:[~2001-02-27 23:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-27 23:00 Xavier Wang [this message]
2001-02-27 23:11 ` Jonathan Larmour
2001-02-28 0:39 ` Xavier Wang
2001-02-28 0:52 ` Jonathan Larmour
2001-02-28 2:22 ` Xavier Wang
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='004f01c0a152$d298e6c0$1c2414ac@realtek.com.tw' \
--to=xavierwang@ms19.url.com.tw \
--cc=ecos-discuss@sources.redhat.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).