[openbeos] Re: monitoring dprintf
- From: "Alexander G. M. Smith" <agmsmith@xxxxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Sat, 24 Apr 2004 23:04:42 -0400 EDT
Eli Green wrote on Sat, 24 Apr 2004 22:53:19 -0400 EDT:
> Is there a way to view the output of dprintf's without hooking up a
> serial cable? The dprintf thread is taking a massive amount of CPU and
> I'd like to know what it's saying. =)
Hacked up from the notes for AGMSRAMDiskDevice:
Viewing the Log:
If you want to see what's happening, and perhaps catch any error messages, you
need to turn on debug logging. Reboot the computer, then just when BeOS is
starting to boot, hit the space bar. A text menu should appear, pick the safe
mode options from it, and then from the submenu, pick the Enable Console
Debugging option. Now debug messages will be appended to the file
/var/log/syslog and will also spew out the serial port at 19200 baud (which is
why they are slow). You can watch the messages live by using the Terminal
command "tail --retry --follow=name /var/log/syslog".
- Alex
- References:
- [openbeos] monitoring dprintf
- From: Eli Green
Other related posts:
- » [openbeos] monitoring dprintf
- » [openbeos] Re: monitoring dprintf
- [openbeos] monitoring dprintf
- From: Eli Green