Iliad freezing on error

Hey all,

It turns out my problems had nothing to do with OS X - if I run a
clean copy of Iliad, everything works fine. But if there's a bug in my
code, and there obviously is, I never get the error response. It just
sits there. I tried starting the server from gst instead of gst-remote
and the same thing happens - no response. Any ideas where I could
start looking? How does everybody else debug this thing?

Thanks,
Eli

Le mercredi 03 mars 2010 à 10:36 +0100, Eli Green a écrit :
> Hey all,
>
> It turns out my problems had nothing to do with OS X - if I run a
> clean copy of Iliad, everything works fine. But if there's a bug in my
> code, and there obviously is, I never get the error response. It just
> sits there. I tried starting the server from gst instead of gst-remote
> and the same thing happens - no response. Any ideas where I could
> start looking? How does everybody else debug this thing?

It seems there is a problem in recent versions of Iliad with error
handling.

http://code.google.com/p/iliadproject/issues/detail?id=6

I'll take a look at this issue this afternoon.

Nico

The bug came from the fact that the error hanlding mode was in the
application.

When errors occured in the application initialization, you couldn't get
the error handler to catch and print the error.

So I decided to put the mode to ILErrorHandler directly. This has 2
advantages:

- It fixes the bug :D
- You don't have to turn each application to one mode or another.

Now you can switch to deployment mode with:
Iliad.ILErrorHandler deploymentMode

Cheers!

Nico

My embarrassment knows no bounds. I located the problem, which was an
endless loop in a simple accessor. Ugh. Sorry. :)

2010/3/3 Nicolas Petton <[hidden email]>:

Le mercredi 03 mars 2010 à 13:29 +0100, Eli Green a écrit :
> My embarrassment knows no bounds. I located the problem, which was an
> endless loop in a simple accessor. Ugh. Sorry. :)

Hehe, no problem. It made me fix a bug anyway :)

Cheers!

Nico