This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Porting Problem with stdout
On Mon, Jan 19, 2004 at 08:49:22AM -0800, dries wrote:
> Andrew Lunn wrote :
>
> >
> > This is a classic dereferenced null pointer. The way to track this
> > down is to use gdb. Look at the memory at 0x0 and check it has the
> > correct contents. Then single step a few lines of code. Then check the
> > contents again. At some point the memory around 0x0 will change. Look
> > at the lines of code that caused the problem.
> >
>
> OK, it must be a NULL pointer but the point is how to catch it, it
> is probably in the printf function. Our problem at this moment is
> that we have no gdb connection, today we will try if it is as simple
> as to enable gdb support and run again. . . . . wish me luck !!
Actually, its more likely to be in you serial driver i think.
See if diag_printf() works correctly. diag_printf() and printf() have
different code paths and only share the device driver.
Andrew
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss