I assume they call WCETRACEGETENV() as a first call in the main() function. I gave up and called WCETRACESET(WCE_ALL) in my program. But it seems to me that cegcc prologue code, or library init code should call WCETRACEGETENV() to allow tracing of arbitrary programs without modifying them, and also allowing tracing to produce output before the main() is even executed (so prologue and init code can be traced).
Thanks, Pawel. On Wed, Sep 3, 2008 at 12:23 PM, Danny Backx <[EMAIL PROTECTED]> wrote: > Maybe the (ush) setenv command did what the ush tools expect, but not > what our newlib expects ? > > Danny > > On Tue, 2008-09-02 at 23:03 -0700, Pawel Veselov wrote: >> Hi ! >> >> I'm really sorry, but I can't any meaningful source on how to >> make tracing print what it suppose to print... I'm using 'ush' to execute >> my binaries, I did 'setenv WCETRACE_DEBUGGER all' and >> 'setenv WCETRACE all' and nothing is coming out. The funny thing is that >> all the utilities that came with 'ush' started tracing, but not my program... >> >> Any hints? Pretty please? :) ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Cegcc-devel mailing list Cegcc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cegcc-devel
