From: Ian Gilmour <ian.gilmour@ffei.co.uk>
To: "'insight@sources.redhat.com'" <insight@sources.redhat.com>
Subject: insight & ddd
Date: Fri, 29 Nov 2002 08:30:00 -0000 [thread overview]
Message-ID: <334D05460466D311A5E8009027AC788603880952@hhmail1.hh.ffei.co.uk> (raw)
I've used ddd for a while and am just starting off using insight.
I've got a gdb user macro in ~/.gdbinit that runs fine using
powerpc-eabi-gdb (insight version) but when I run the same
macro using ddd as the front-end (and insight as the gdb backend) I get...
-----------------------------
GNU DDD 3.3 (i586-mandrake-linux-gnu), by Dorothea Lütkehaus and Andreas
Zeller.
Copyright © 1995-1999 Technische Universität Braunschweig, Germany.
Copyright © 1999-2001 Universität Passau, Germany.
setting up printing options...
(gdb) psimddd
Connected to the simulator.
Breakpoint 1 at 0x36d8: file twothreads.c, line 25.
void cyg_user_start(void);
Breakpoint 2 at 0x788c: file
/usr/local/tools/src/ecosCVS/ecos/packages/infra/current/src/tcdiag.cxx,
line 261.
void cyg_test_exit(void);
Breakpoint 3 at 0x600c: file
/usr/local/tools/src/ecosCVS/ecos/packages/infra/current/src/buffer.cxx,
line 727.
void cyg_assert_fail(char *, char *, cyg_uint32, char *);
Segmentation fault
------------------------------
psimddd contains...
------------------------------
define psimddd
target sim -o '/iobus/pal@0xf0001000/reg 0xf0001000 32'
load
rbreak cyg_user_start
rbreak cyg_test_exit
rbreak cyg_assert_fail
end
------------------------------
Any clues as to whether this is a ddd problem, an insight problem or my
config?
Do I need a raw version of gdb to overcome it?
Any ideas?
N.B. Host is linux.
cheers,
Ian
next reply other threads:[~2002-11-29 16:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-29 8:30 Ian Gilmour [this message]
2002-12-02 8:41 ` Keith Seitz
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=334D05460466D311A5E8009027AC788603880952@hhmail1.hh.ffei.co.uk \
--to=ian.gilmour@ffei.co.uk \
--cc=insight@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).