Re: [ECOS] Debugging techiques

Re: [ECOS] Debugging techiques

[Boris V. Guzhov]

Thanks. It works.
I think that it is useful to include in documentation more detailed
description
of the debugging techniques.

Boris Guzhov

>
>If you want all tracing to be printed immediately, change the
>implementation from buffered to "simple" or "fancy", i.e. disable
>CYGDBG_INFRA_DEBUG_TRACE_ASSERT_BUFFER in the infra package and enable e.g.
>CYGDBG_INFRA_DEBUG_TRACE_ASSERT_FANCY.
>
>Other CDL options in this area may be of interest, such as the buffer size
>etc.
>
>> How to use Function Tracing (CYG_REPORT_FUNCTION() and others)?
>
>You mean in your own functions? Have a look at the header file
>infra/VERSION/include/cyg_trac.h in your component reposistory. There's
>plenty of comments at the top. Eventually we want to get this in the
>"proper" documentation, but we haven't yet.
>
>Jifl
>--
>Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS  Tel: +44 (1223) 728762
>"Plan to be spontaneous tomorrow."  ||  These opinions are all my own fault
>

Re: [ECOS] debugging techiques

[Jonathan Larmour]

> zhang wrote:
> But an error occured ,and it said that :
> 
>     make[1] ***[src/mem/memfixed.o.d] Error 1
>     make[2] ***[build] Error 2
> 
> I do not know why and which cause the errors ,so could someone help me ?

Are you sure there wasn't some information on the lines before this
describing where the real problem lies? Try giving the output from the
final gcc build command line onwards.

Jifl
-- 
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS  Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow."  ||  These opinions are all my own fault

[ECOS] debugging techiques

[zhang]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 835 bytes --]




Hi all! My host Linux Redhat 6.1, my target - pc 
linux. I like to use the debugging tracing, but I have some 
problems. I did following: mkdir linux-s cd 
linux-s ecosconfig new linux In ecos.ecc I have 
changed: cdl_component CYGPKG_INFRA_DEBUG { ...  user_value 
1 ... }; cdl_component CYGDBG_USE_ASSERTS 
{ ...     user_value 0 ... }; cdl_component 
CYGDBG_USE_TRACING { ...     user_value 
1 ... }; Other options I did not change. ecosconfig 
check ecosconfig tree make
 
But an error occured ,and it said that :
 
    make[1] ***[src/mem/memfixed.o.d] Error 
1
    make[2] ***[build] Error 2 
 
I do not know why and which cause the errors ,so could someone 
help me ?
 
Thanks a lot!
Thanks in advance for any help you might be able to 
provide me.

Re: [ECOS] Debugging techiques

[Jonathan Larmour]

"Boris V. Guzhov" wrote:
> 
> Why there is no tracing printing?

That's because the default tracing implementation is buffered tracing.
trace output will not be printed by default. It gets printed when an assert
fails, or you force it to print by calling CYG_TRACE_PRINT() in your source
code. You can also configure it to print when full though this isn't the
default.

If you want all tracing to be printed immediately, change the
implementation from buffered to "simple" or "fancy", i.e. disable 
CYGDBG_INFRA_DEBUG_TRACE_ASSERT_BUFFER in the infra package and enable e.g.
CYGDBG_INFRA_DEBUG_TRACE_ASSERT_FANCY.

Other CDL options in this area may be of interest, such as the buffer size
etc.
 
> How to use Function Tracing (CYG_REPORT_FUNCTION() and others)?

You mean in your own functions? Have a look at the header file
infra/VERSION/include/cyg_trac.h in your component reposistory. There's
plenty of comments at the top. Eventually we want to get this in the
"proper" documentation, but we haven't yet.

Jifl
-- 
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS  Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow."  ||  These opinions are all my own fault

[ECOS] Debugging techiques

[Boris V. Guzhov]

Hi all!

My host Linux Redhat 6.2, my target - linux-synthetic.

I like to use the debugging tracing, but I have some problems.

I did following:

mkdir linux-s
cd linux-s
ecosconfig new linux

In ecos.ecc I have changed:

cdl_component CYGPKG_INFRA_DEBUG {
...
 user_value 1
...
};

cdl_component CYGDBG_USE_ASSERTS {
...
    user_value 0
...
};

cdl_component CYGDBG_USE_TRACING {
...
    user_value 1
...
};

Other options I did not change.

ecosconfig check
ecosconfig tree
make

Then I have built hello.c test (from examples) and have run it.

It's result:
Hello, eCos world!

Why there is no tracing printing?

How to use Function Tracing (CYG_REPORT_FUNCTION() and others)?

Thanks in advance for any help you might be able to provide me.

Boris Guzhov