From: Hans-Wolfgang Loidl <hwloidl@informatik.uni-muenchen.de>
To: DJ Delorie <dj@redhat.com>
Cc: gdb@sourceware.org, drow@false.org
Subject: Re: gdb support for m32c?
Date: Fri, 10 Mar 2006 22:45:00 -0000 [thread overview]
Message-ID: <20060310234511.7b55e761@anagni.tcs.ifi.lmu.de> (raw)
In-Reply-To: <200603102130.k2ALUJ3M004786@greed.delorie.com>
Hi DJ,
In the meantime I managed to build the m32c simulator from the CVS HEAD,
and with that version I can now run simple C programs, and also some
programs compiled via C from out high-level language
So, I'm a happy user (for now)!
I noticed, though, that the simulator can't handle argv input: it gives
a null pointer reference.
Any patches that you have, and other hints on using it tools etc would
be very welcome!
Cheers,
--
HW
On Fri, 10 Mar 2006 16:30:19 -0500
DJ Delorie <dj@redhat.com> wrote:
>
> > > I now checked out the HEAD of the gdb cvs rep with the m32c code
> > > in sim. Does "not supported yet" mean that the simulator itself
> > > doesn't work, or just that some GDB features don't work, yet?
> > > As said, at the moment I'd only need the simulator, and I'd happy
> > > with a version even if it's still a bit unstable.
> >
> > The simulator should be fine, as far as I know.
>
> Alas, it needs some patches, although they're minor. I use the
> simulator a LOT so it's fairly stable.
>
> I missed that the m32c sim had been approved. I'm supposed to be the
> m32c sim maintainer but Jim didn't add me as part of the commit
> process. How to proceed?
>
> Also, while I can get the simulator to build, it currently doesn't get
> that far because it has a dependency on gdb being at least configured,
> which doesn't happen yet. That's why I didn't notice my builds
> suddenly including the simulator :-P
next prev parent reply other threads:[~2006-03-10 22:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-10 21:30 DJ Delorie
2006-03-10 22:45 ` Hans-Wolfgang Loidl [this message]
2006-03-10 22:55 ` DJ Delorie
2006-03-10 23:12 ` Hans-Wolfgang Loidl
2006-03-10 23:21 ` DJ Delorie
2006-03-14 2:23 ` Daniel Jacobowitz
2006-03-14 2:38 ` DJ Delorie
-- strict thread matches above, loose matches on Subject: below --
2006-03-08 22:11 Hans-Wolfgang Loidl
2006-03-09 3:24 ` Daniel Jacobowitz
2006-03-09 14:41 ` Hans-Wolfgang Loidl
2006-03-09 15:00 ` Daniel Jacobowitz
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=20060310234511.7b55e761@anagni.tcs.ifi.lmu.de \
--to=hwloidl@informatik.uni-muenchen.de \
--cc=dj@redhat.com \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
/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).