public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jlarmour@cygnus.co.uk>
To: Lance Uyehara <lance@nuvomedia.com>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] Turning off gdb
Date: Fri, 05 Nov 1999 12:39:00 -0000	[thread overview]
Message-ID: <38234083.EE2155EC@cygnus.co.uk> (raw)
In-Reply-To: <3.0.5.32.19991105111132.00a61100@mail.nuvomedia.com>

Lance Uyehara wrote:
> At 09:55 AM 11/3/99 -0800, Lance Uyehara wrote:
> >I'm trying to build a minimum sized ecos codeset, and have run into some
> >odd behavior in the configuration tool.
> >
> >Since CYGDBG_HAL_DEBUG_GDB_THREAD_SUPPORT and
> >CYGDBG_KERNEL_DEBUG_GDB_THREAD_SUPPORT require each other, I can't turn off
> >either without crashing the configuration tool (in win32).

It crashes the config tool? Obviously that shouldn't happen. Does it
actually cause an application error? What if you disable "Suggest fixes for
consistency check failures" under Tools->Options, does that allow you to
unset them both? Or possibly set the "Check rules" in the same place to
"Never".

What *should* happen is that disabling one of them should pop up a dialog
box saying something like "Yadayada requires foobarfoobar, disable? Yes/No"

> >But I look in the .cfg file and see nothing which I associate with these
> >settings. So how can I turn this off in the configuration tool?
>
> I guess the real question is what are the names of the things to put into
> the .cfg file to turn off settings in the configuration tool (win32). Using
> -enable and -disable.

When you have saved the configuration, you can manually edit the options by
going into the build tree directory (i.e. the place you saved the
configuration), and editting the pkgconf/hal.h file. The two options you are
after can be disabled in there.

Jifl
-- 
Cygnus Solutions, 35 Cambridge Place, Cambridge, UK.  Tel: +44 (1223) 728762
"I used to have an open mind but || Get yer free open source RTOS's here...
 my brains kept falling out."    || http://sourceware.cygnus.com/ecos
Help fight spam! http://spam.abuse.net/  These opinions are all my own fault

  reply	other threads:[~1999-11-05 12:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-01 15:54 [ECOS] bogus clock interrupt handling numbers? Clint Bauer
1999-11-03  9:15 ` Gary Thomas
1999-11-03  9:57   ` [ECOS] Turning off gdb Lance Uyehara
1999-11-05 11:12     ` Lance Uyehara
1999-11-05 12:39       ` Jonathan Larmour [this message]
1999-11-05 12:59         ` Lance Uyehara
1999-11-05 13:08           ` Gary Thomas
1999-11-05 13:13             ` Lance Uyehara
1999-11-05 13:21               ` Gary Thomas

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=38234083.EE2155EC@cygnus.co.uk \
    --to=jlarmour@cygnus.co.uk \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=lance@nuvomedia.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).