This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: limit on the number of diag_printf(s) ????


On Mon, Apr 12, 2004 at 06:01:54PM +0100, Bart Veer wrote:

>>> The problem tends to be that the diag_printf() and gdb traffic
>>> can interfere with each other. After all they share the same
>>> communication hardware, usually a uart. If you put a
>>> diag_printf() in the wrong place then it may e.g. overwrite a
>>> buffer that already contains a partial response to a gdb
>>> request.
> 
>  Grant> But, that failure occurs at run-time, not at load-time.
>  Grant> Right?
> 
> If the diag_printf()'s are in the application then yes. In this case
> it is the gdb stubs that are causing problems so I had assumed the
> diag_printf()'s were being added to RedBoot rather than the
> application. That makes the distinction between run-time and load-time
> rather blurred.

Of course you're right.  I misread the OP and thought the
printf() that was breaking the camel's back was in the loaded
application.

-- 
Grant Edwards
grante@visi.com

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]