Beam not work hrev48547

Forum thread started by kim1963 on Tue, 2014-12-23 04:51

Hrev48541 - work fine. When broken ?
https://dev.haiku-os.org/ticket/11655

‹ 10 years from last login - where are we now? Native resolution with intel extreme ›

Comments

Re: Beam not work hrev48547

by kim1963 - 2014-12-23 05:07

BLocker: call debugger() when unlocking from another threadhrev48542
BeOS did allow other threads than the owner to unlock a BLocker (the be
book says so). We did not, and silently ignored the unlock attempt in
this case, probably resulting in a deadlock of applications using the
feature.
Call debugger instead so:
The problem is made visible for such apps
The debugger call is continuable so the app can be run, still
Will help making a decision on what to do here (follow BeOS or change
behavior) and make a final decision for #6400.

Beam - can be thrown away?

Re: Beam not work hrev48547

by humdinger - 2014-12-23 09:04

You know you could have people subscribe to your RSS feed, so they can keep up with your tireless endeavours on the bug tracker: https://dev.haiku-os.org/timeline?ticket=on&ticket_details=on&max=50&aut...

Re: Beam not work hrev48547

by kim1963 - 2014-12-23 09:28

Welcome to the Haiku shell.

~> /boot/home/config/non-packaged/apps/BeZillaMail/BeZillaMail
runtime_loader: /boot/home/config/non-packaged/apps/BeZillaMail/lib/libnspr4.so: Could not resolve symbol '_get_system_info'
resolve symbol "_get_system_info" returned: -2147478780
runtime_loader: /boot/home/config/non-packaged/apps/BeZillaMail/lib/libnspr4.so: Troubles relocating: Symbol not found
~>

hrev48547 - no normal mail client ...

Re: Beam not work hrev48547

by kim1963 - 2014-12-23 10:30

by pulkomandy

Beam package updated in hrev48551. Should work again.

by kim1963

Thanks! Good job.