Hi,
this is more of an open discussion topic than a concrete question but
hopefully someone has a good idea about this:
I got a bug report of a non-crash bug I cannot reproduce and where I
do not even know where to start looking. The only hint is a line in
the console.log:
***
El 09/07/2008, a las 12:13, Ruotger Skupin escribió:
So an exception got thrown for a pretty obvious reason, but where?
Could be anywhere, even in WebKit (which we use). Is there any
chance to get near the culprit without a stack trace (which I don't
have)?
This question is more
On Jul 9, 2008, at 5:13 AM, Ruotger Skupin wrote:
this is more of an open discussion topic than a concrete question
but hopefully someone has a good idea about this:
I got a bug report of a non-crash bug I cannot reproduce and where I
do not even know where to start looking. The only hint
I would rather not try to teach my users gdb...
Ruotger
Am 09.07.2008 um 12:31 schrieb Joan Lluch (casa):
El 09/07/2008, a las 12:13, Ruotger Skupin escribió:
So an exception got thrown for a pretty obvious reason, but where?
Could be anywhere, even in WebKit (which we use). Is there any
On Wed, Jul 9, 2008 at 10:13 PM, Ruotger Skupin [EMAIL PROTECTED] wrote:
*** -[NSCFDictionary initWithObjects:forKeys:count:]: attempt to insert nil
value at objects[0] (key: NSFont)
So an exception got thrown for a pretty obvious reason, but where? Could be
anywhere, even in WebKit (which we
On 9 Jul '08, at 5:32 AM, Ruotger Skupin wrote:
I would rather not try to teach my users gdb...
My MYUtilities library includes support for getting exception
backtraces at runtime and reporting them to the user (see
ExceptionUtils.h).
