Re: jsdIDebuggerService crashing FF 2.0

James Ross wrote:
> John Bandhauer wrote:
>> XPConnect did its job exactly right here. The *real* bug here is in 
>> jsd_xpc.cpp. That bug ought to be fixed.
>>
>> But first. Before spreading the notion that XPConnect is broken, you 
>> should try to understand what job it is doing.
> 
> I didn't say it was broken here, I said I don't *trust* it here. That's 
> from experience of it being broken in other places, and I find your 
> arrogant and patronising attitude very worrying.
> 

Ha! Let's not get too serious here.

I'm not sure why you should find my attitude worrying; I'm not an active 
contributor, so I'm not likely to do any new damage to anything.

I was merely trying to offer some insight into code that I wrote a long 
time ago. I won't speak to the charge of arrogance :) But, I will say 
that what you called "patronising" was simply my response to seeing 
people working around a very real software defect when filing a bug (and 
perhaps finding and fixing the problem) was in order. I'm sorry if my 
explanation of the XPConnect behavior was too elementary for you, but I 
assume that other people might read it and I was trying to explain it in 
a reasonable and complete fashion.

Your statements... "(Personally, I'd have thought XPConnect should shit 
itself long before this got to JSD code, but I've also learnt to never 
trust XPConnect to do its job right.)" ...suggest that you didn't 
understand what XPConnect was really doing in this case.

I'd be more impressed by *active* mozilla developers if *someone* went 
to the trouble of filing a bug on JSD (citing the info I gave 
previously) so that this bug perhaps gets fixed one day.

John.