From: Gary Thomas <gthomas@redhat.com>
To: Nicholas_Karagas@cirilium.com
Cc: insight@sourceware.cygnus.com, ecos-discuss@sourceware.cygnus.com
Subject: RE: [ECOS] twothreads in PPC simulator
Date: Thu, 06 Jul 2000 10:45:00 -0000 [thread overview]
Message-ID: <XFMail.000706114538.gthomas@redhat.com> (raw)
In-Reply-To: <OF66284EF4.A093FC5D-ON07256914.00582528@cirilium.com>
Try enabling GDB stubs in your application. Currently, most targets need special
support in order to provide thread-specific debugging. This can be enabled
by turning on GDB stubs within the downloaded program itself.
Note: we are improving most targets so that this will no longer be necessary,
i.e. you'll get thread debugging without needing to include GDB stubs in your
image. I don't know if this will be the case for the PPC simulator though.
On 06-Jul-00 Nicholas_Karagas@cirilium.com wrote:
> Not sure where to go with this one, but I thought I'd try you guys first...
>
> I'm trying to use eCos for PowerPC, and right now I don't have the
> hardware, so I was configuring it for the PowerPC simulator. I built the
> twothreads example program, and tried debugging it in Insight. My problem
> is that when I interrupt the program while it is running, I cannot get
> information on the threads (i.e. thread-specific breakpoints don't work,
> thread list is empty, 'info threads' in console window doesn't return
> anything). The same thing happens in -nw mode. I double-checked, and eCos
> is configured for multithreaded debugging (I just used the default PowerPC
> simulator template, and added the IP stack package). My versions are as
> follows:
>
> gcc - 2.95.2 19991024
> gdb - 5.0
> eCos - 1.3.1
> host - i686-pc-cygwin (on NT 4.0)
> target - powerpc-eabi
>
> Thanks for any help.
>
> Nicholas Karagas
> Associate Software Engineer
> Cirilium Corporation
> Tempe, AZ
> (480) 317-1144
>
next prev parent reply other threads:[~2000-07-06 10:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-06 9:18 Nicholas_Karagas
2000-07-06 10:45 ` Gary Thomas [this message]
2000-07-06 23:34 ` [ECOS] " Jesper Skov
2000-07-06 14:42 Nicholas_Karagas
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=XFMail.000706114538.gthomas@redhat.com \
--to=gthomas@redhat.com \
--cc=Nicholas_Karagas@cirilium.com \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=insight@sourceware.cygnus.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).