This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: limit on the number of diag_printf(s) ????
>>>>> "Grant" == Grant Edwards <grante@visi.com> writes:
Grant> On Mon, Apr 12, 2004 at 05:26:40PM +0100, Bart Veer wrote:
Roman> I am trying to get a port of Redboot running, right now I
Roman> am dealing with single stepping. At this point in the debug
Roman> process I can no longer use a BDM (it permanently changes
Roman> the core behavior) so I have resorted to some well placed
Roman> diag_printf(s) to give me clues. If I only have 2 or less
Roman> diag_printf(s) all works fine. as soon as I add the 3rd
Roman> one, gdb (insight) will not load my application, it just
Roman> comes right back....
Roman> does anyone know what is the limiting factor here ????
>> 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.
Bart
--
Bart Veer eCos Configuration Architect
http://www.ecoscentric.com/ The eCos and RedBoot experts
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss