Dear all,
I am running a custom application package on fiasco using a serial line (no keyboard/screen) and I intermittently get faults caused by printf. I notice that on disassembling the code around the error that the function is called writev in ulibc. Has anyone experienced something similar before?
Thanks, ramya
On Mon Sep 01, 2014 at 16:37:44 +0000, Masti Ramya Jayaram wrote:
I am running a custom application package on fiasco using a serial line (no keyboard/screen) and I intermittently get faults caused by printf. I notice that on disassembling the code around the error that the function is called writev in ulibc. Has anyone experienced something similar before?
Not that I could remember. Just happens for a standard printf("foo\n")?
Adam
No, it would occur randomly. I realized I had some mismatch in function prototypes with arrays. Fixing that got rid of the problem.
Thanks, Ramya ________________________________________ From: l4-hackers [l4-hackers-bounces@os.inf.tu-dresden.de] on behalf of Adam Lackorzynski [adam@os.inf.tu-dresden.de] Sent: 02 September 2014 00:00 To: l4-hackers@os.inf.tu-dresden.de Subject: Re: Fault in function writev (ulibc)
On Mon Sep 01, 2014 at 16:37:44 +0000, Masti Ramya Jayaram wrote:
I am running a custom application package on fiasco using a serial line (no keyboard/screen) and I intermittently get faults caused by printf. I notice that on disassembling the code around the error that the function is called writev in ulibc. Has anyone experienced something similar before?
Not that I could remember. Just happens for a standard printf("foo\n")?
Adam -- Adam adam@os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/
_______________________________________________ l4-hackers mailing list l4-hackers@os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
l4-hackers@os.inf.tu-dresden.de