This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: trace and assert
- To: james chen <james_ch1 at sina dot com>
- Subject: Re: [ECOS] trace and assert
- From: Jonathan Larmour <jlarmour at redhat dot com>
- Date: Tue, 17 Jul 2001 16:43:26 +0100
- Cc: ecos-discuss at sourceware dot cygnus dot com
- Organization: Red Hat UK Ltd.
- References: <000701b27af0$767a7020$c408aa0a@inc.inventec>
james chen wrote:
>
> eCos has supported trace and assert. now I want when a assert failed, it
> will output diagnostic info and GDB stop at assert code. Can I replace
> 'for(;;);' with 'breakpoint()' in cyg_assert_fail?
Yes - it's open source! Although that function only exists if you have
included GDB stubs in your app I believe.
> Another question, what is the difference between simple.cxx, fancy.cxx
> and null.cxx( infra\current\src ), if I select all in eCos Configuration
> Tool, which will be valid or all are valid?
I actually just fixed that, and it will appear publically shortly. Choose
only one for now.
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
Come to the Red Hat TechWorld open source conference in Brussels!
Keynotes, techie talks and exhibitions http://www.redhat-techworld.com/