[openbeos] Re: Haiku image not working?

On 2006-12-23 at 13:09:44 [+1300], Ryan Leavengood <leavengood@xxxxxxxxx> 
wrote:
> On 12/22/06, Stephan Assmus <superstippi@xxxxxx> wrote:
> >
> > I'd probably save my changes somewhere, svn revert everthing and see if it
> > works then. That way you know if the problem is in your changes or not. (I
> > don't quiet understand which build factory image you mean.... if it is the
> > current image, then the problem *is* in your changes, no?)
> 
> The image I downloaded from the build factory works, and when I
> swapped in my new app_server it didn't. So it is definitely a problem
> in my code. But I have no idea what as this is incredibly hard to
> debug. To make matters worse the mail_daemon just caused a KDL on my
> R5 development box and on reboot the app_server seemed to lock up
> after a few minutes. Such joy. I'm writing this email on my Windows
> laptop.

I was a die hard BeMail user for many years, and when I still used MDR, it 
worked fine. But I have since switched to Beam, which is a very powerful and 
reliable piece of software.

The only reason I remember my R5 install being unstable is when I didn't have 
this line in my ~/config/settings/kernel/drivers/kernel:

disk_cache_size 32768            # max number of blocks to cache

I think lower values also work good, like 16384, don't remember why I put it 
up that high.

> It is a little sad when my Windows laptop is much more reliable than
> my BeOS box. It could be the hardware though (well that mail_daemon
> KDL is definitely a BeOS bug.)
> 
> I'll keep working on this after I eat some dinner.
> 
> I'm going to do a lot of serial output to see where things stop in the
> app_server.

I had QEMU going at one point so that I saw any normal printf() from the apps 
in the emulation in the Terminal that I started QEMU from. I think it was 
something like --serial=stdio. Maybe someone else can chime in. Might be 
easier than real serial debugging.

Best regards,
-Stephan

Other related posts: