Author Topic: Debugging 101  (Read 1514 times)

caution

  • Newbie
  • *
  • Posts: 1
    • View Profile
Debugging 101
« on: October 27, 2004, 07:40:27 pm »
Deciding to move off stable OZ 3.2 onto 3.5.1, I now have a Zaurus SL-5500D that seems to consistently freeze up all the time. I understand that this is not meant to be a stable release, though what can be done contribute to the debugging process?

Not being OZ guru, I have not seen much explaination of what can be done to report and diagnose problems. Hence I thought it would be a good idea to raise these questions.

* What is the best way for people to report issues in the Zaurus?

* Is sourceforge the best place to raise bug reports?

I understand that screenshots, error messages, and history explainations work well most of the time, though in my case, Zaurus freezes, so no chance for these methods.

Is enabling syslogd an effective method for capturing any future errors?? Are theere any key log files that can be created for advanced debugging???

Thanks

lardman

  • Hero Member
  • *****
  • Posts: 4512
    • View Profile
    • http://people.bath.ac.uk/enpsgp/Zaurus/
Debugging 101
« Reply #1 on: October 28, 2004, 05:37:04 am »
Quote
Is enabling syslogd an effective method for capturing any future errors??

Might be, can't hurt to try it.

Quote
I understand that screenshots, error messages, and history explainations work well most of the time, though in my case, Zaurus freezes, so no chance for these methods.

Can you ssh in? That way you could at least see what is/isn't running, etc.

Quote
* What is the best way for people to report issues in the Zaurus?

https://www.oesf.org/forums/inde...?showtopic=7211


Simon
C750 OZ3.5.4 (GPE, 2.6.x kernel)
SL5500 OZ3.5.4 (Opie)
Nokia 770
Serial GPS, WCF-12, Socket Ethernet & BT, Ratoc USB
WinXP, Mandriva