My experience on Leopard has been that any input which is not
syntactically correct Ruby will crash Shoes (Curious before it can
load. The error is:
Exception Type: EXC_BAD_ACCESS (SIGABRT)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000048
Crashed Thread: 0
Thread 0 Crashed:
0 libSystem.B.dylib 0x930310ea __kill + 10
1 libSystem.B.dylib 0x930a83f2 raise + 26
2 libSystem.B.dylib 0x930b79af abort + 73
3 libruby.dylib 0x000f3415 rb_check_type + 0
4 libruby.dylib 0x00174206 ruby_posix_signal + 372
5 libSystem.B.dylib 0x9302f5eb _sigtramp + 43
6 ??? 0xffffffff 0 + 4294967295
7 libruby.dylib 0x0010417a
rb_with_disable_interrupt + 5848
8 libruby.dylib 0x00104f22
rb_with_disable_interrupt + 9344
9 libruby.dylib 0x00105157 rb_apply + 553
10 libruby.dylib 0x00105188 rb_funcall + 44
11 libshoes.dylib 0x00460421 shoes_app_visit + 387
12 libshoes.dylib 0x004607d8 shoes_app_goto + 132
13 libshoes.dylib 0x004600aa shoes_app_loop + 133
14 libshoes.dylib 0x0045fd7b shoes_app_start + 80
15 libshoes.dylib 0x00483658 shoes_load + 92
16 libshoes.dylib 0x004837b4 shoes_start + 313
17 shoes-bin 0x00001f98 main + 86
18 shoes-bin 0x00001eea _start + 228 (crt.c:272)
19 shoes-bin 0x00001e05 start + 41
I hope that helps.
— Jeremy
On Feb 27, 2008, at 11:29 AM, why the lucky stiff wrote:
On Wed, Feb 27, 2008 at 11:56:54AM +0100, Simone D. wrote:
Which is the best way to debug Shoes to understand what is not
working
(meaning that Shoes.app doesn't start)?
I recommend DebugView:
<http://www.microsoft.com/technet/sysinternals/Miscellaneous/DebugView.mspx
>
You can then use Shoes.debug and Shoes.p to send messages to
DebugView from your Shoes app.
Shoes.debug("Creating katamari...")
Shoes.p katamari_object
If the thing is crashing before it gets to any of this, post a
script that breaks along with the version name of Shoes you're
using.
_why
