FogBugz Technical Support

A forum for technical support discussion related to Fogbugz.
The current FogBugz Knowledge Base can be found at http://help.fogcreek.com/fogbugz.

Posts by Fog Creek Employees are marked:

Documentation
Release Notes
Network Status

BugScout Problem

(Reposting this since the way these forums work, new stuff isn't marked and I think it just got over looked...)

The biggest problem I've found with BugScout is that it doesn't seem to catch everything.  If I throw an exception (by hand), it catches that just fine.  But there are tons of other crashes that just go right past it that I don't understand.

Like one today where the user got:

Common Language Runtime Debugging Services

Application has generated an exception that could not be handled.

Process id = bla bla  Thread id = bla bla

But it never got caught.  In this case it even says it was a CLR exception.  So I don't get why I didn't catch the dang thing.

I'm doing this sorta thing before my application main loop:

      Application.ThreadException += new ThreadExceptionEventHandler(eh.OnThreadException);


ThreadException claims to be the event raised when an unhandled exception occurs.  Works when I purposely throw one.

The other extenuating circumstance, so to speak, is that my C# .NET managed code calls into unmanaged code (in the form of a DLL).  It has a very wide interface (lots of functions).  Is it possible that exceptions thrown there will not be caught?  If so, is there something I can do to catch these?  Do I have to rig up the ActiveX version of BugScout as well as the .NET version?

-- David
David Whatley Send private email
Tuesday, March 8, 2005
 
 
Hi David,

I don't really understand what you mean.  BugzScout doesn't catch exceptions, it's just a way for you as the programmer to handle them...

So you would write..

try {
 // some code
}
catch(...)
{
  // create bugzscout here and submit it to my fogbugz install
}
Michael H. Pryor Send private email
Tuesday, March 8, 2005
 
 
The point is to catch the exceptions that bubble up to the top and were not handled.  Otherwise you are not really catching anything except what you expect.  You want to have one spot you can put this.

I can't put a try catch around the whole thing because the Application implementation of DoEvents() or Run() has a catch in it that handles exceptions by just giving the user a dialog telling them about the unhandled exception.

-- David
David Whatley Send private email
Tuesday, March 8, 2005
 
 
I guess I don't know enough about the specifics of the .net implementation.  I thought you were explaining a problem with BugzScout...
Michael H. Pryor Send private email
Tuesday, March 8, 2005
 
 
I'm talking about how to use bugscout effectively.

-- David
David Whatley Send private email
Tuesday, March 8, 2005
 
 

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics
 
Powered by FogBugz Bug Tracking and Evidence-Based Scheduling.