Hi,
again following up to my own post...
I am now sure there are two different things.
One is my test program breaking very badly when receiving a signal
during blocking read() from the serial port. I do not know why, but
as this happens on "regular" linux, too, and is not really debuggable
("up" takes me to completely strange addresses), I suspect some kernel
problem here.
The other is that my "real" application already fails when calling read()
from the serial port, even without a signal occuring. There is no message,
the system simply locks up completely.
I did not yet figure out how to debug this properly, but it seems to
be an application problem, because the test application does not behave
like this. (It is not an obvious problem, at least not to me; the device
is opened, a previous write to the device is successful, and the call
to read() is read(astro_serial_dev, &rcvchar, 1); with rcvchar being
a locally declared unsigned char...)
I tried debugging this with gdb and the peedi, but I am not yet able to
debug applications; when issuing "info threads" in gdb, I always get
the message
warning: RMT ERROR : failed to get remote thread list.
(This happens with both gdb-6.6 and gdb 6.3-debian)
In case somebody knows something more about the serial ports, please
let me know.
Regards,
Wolfgang
_______________________________________________
uClinux-dev mailing list
[email protected]
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by [email protected]
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
