From: "Laurie Gellatly" <laurie.gellatly@netic.com>
To: "Carlos Losada" <itel9cl1@yahoo.com>
Cc: <ecos-discuss@ecos.sourceware.org>
Subject: RE: [ECOS] building and debugging
Date: Wed, 21 Feb 2007 10:04:00 -0000 [thread overview]
Message-ID: <OBEELMDOHGDFDEMJCJCJIEHALKAA.laurie.gellatly@netic.com> (raw)
In-Reply-To: <519508.74681.qm@web62310.mail.re1.yahoo.com>
Hi Carlos,
Just before you sent this message I found the problem.
Yes, you're right with the fix.
Appreciate your reply.
Thanks ...Laurie:{)
-----Original Message-----
From: Carlos Losada [mailto:itel9cl1@yahoo.com]
Sent: Wednesday, 21 February 2007 7:58 PM
To: Laurie Gellatly
Subject: Re: [ECOS] building and debugging
Laurie I had the same problem with the indexer until I
provided the path to ecos include directory directly.
Try the following:
Eclipse->Project->Properties
C/C++ Build->GCC C Compiler->Directories
Then type in the absolute path to the ecos include
directory. For example:
C:\cygwin\home\carlos\...\ecos_install\include
Good Luck
Carlos
--- Laurie Gellatly <laurie.gellatly@netic.com> wrote:
> Hi All,
> I've been using eclipse to develop my arm based
> system for some time.
> The application runs multiple threads and I had been
> able to debug them
> reasonably well (the program did not always flow the
> way I expected when
> single stepping and sometimes local variables are
> not able to be displayed).
> What I have now is that although the main thread
> seems to be able to be
> debugged, the other threads have problems.
> I can set a breakpoint in a thread and it will stop,
> but single stepping or
> trying to display local variables etc no longer
> works.
> I've tried various things to fix it including
> reducing the size of the app
> (down to 300K), but without any luck.
>
> Is this a GDB or Eclipse limit or have I had a
> configuration issue?
>
> BTW the indexer has always complained that the
> #include s for the OS files
> could not find yet C does find them.
> Anyone suggest what might be wrong?
>
> Thanks ...Laurie :{)
>
>
> --
> Before posting, please read the FAQ:
> http://ecos.sourceware.org/fom/ecos
> and search the list archive:
> http://ecos.sourceware.org/ml/ecos-discuss
>
>
____________________________________________________________________________
________
Don't pick lemons.
See all the new 2007 cars at Yahoo! Autos.
http://autos.yahoo.com/new_cars.html
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next parent reply other threads:[~2007-02-21 10:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <519508.74681.qm@web62310.mail.re1.yahoo.com>
2007-02-21 10:04 ` Laurie Gellatly [this message]
2007-02-18 17:51 [ECOS] i2c questions Grant Edwards
2007-02-19 7:23 ` [ECOS] building and debugging Laurie Gellatly
2007-02-20 19:32 ` Andrew Lunn
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=OBEELMDOHGDFDEMJCJCJIEHALKAA.laurie.gellatly@netic.com \
--to=laurie.gellatly@netic.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=itel9cl1@yahoo.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).