Where do you write your error when all else fails ?

http://msdn.microsoft.com/msdnmag/issues/05/03/Bugslaye
r/ I would
highly recommend reading up on all of John Robbins'
material
(including his books). The article shows using ADPlus but in
another
article that I don't have a link handy for he shows how to
programmatically take a dump using dbghelp (a quick google
should
bring up some pre-done code for this)


Basically it takes a snap shot of your application (i.e. the
complete
state of your application) you can then get in with a
debugger to look
at thread stacks, parameters being passed to methods,
objects on the
heap, etc. It is much more useful for figuring out what
happenned than
only having an exception. If you happen to be in the
mid-atlantic area
I will be presenting on more "enterprise" level
debugging (including
production applications) at the SC code camp.

Cheers,

Greg

On 8/29/06, Steve W <lslbtconnect.com> wrote:
> Greg,
>
> Sorry to be ignorant but what do you mean by 'take a
minidump' ?
>
> Thanks
>
> Steve
>
> -----Original Message-----
> From: Discussion of development on the .NET platform
using any managed
> language [mailtoOTNET-CL
RDISCUSS.DEVELOP.COM] On Behalf Of gregory young
> Sent: 29 August 2006 17:47
> To: DOTNET-CLRDISCUSS.DEVELOP.COM
> Subject: Re: [DOTNET-CLR] Where do you write your error
when all else fails
> ?
>
> I take a minidump (well I generally do this anyways)
... It gives you
> alot more information than just the exception that
occurred.
> Afterwords I commit suicide in the app.
>
> Cheers,
>
> Greg
>
> On 8/29/06, Greg Robinson <gregcds-am.net> wrote:
> > Text file and\or you can auto email it, which is
what we do.
> >
> >
> >
> > -----Original Message-----
> > From: Discussion of development on the .NET
platform using any managed
> > language [mailtoOTNET-CL
RDISCUSS.DEVELOP.COM]On Behalf Of Steve W
> > Sent: Tuesday, August 29, 2006 12:30 PM
> > To: DOTNET-CLRDISCUSS.DEVELOP.COM
> > Subject: [DOTNET-CLR] Where do you write your
error when all else fails
> > ?
> >
> >
> > I have an error handling mechanism in a windows
service that does this :
> >
> > 1.  Try and write error to db - catch any
exception raised
> > 2.  If exception raised try and write to
application log
> >
> > If 2 raises an exception where should I try and
write the error
> information
> > next ?
> >
> > I was thinking of a text file in the user's
temporary directory - does
> > anyone have any better suggestions ?
> >
> > Thanks
> >
> > Steve
> >
> > ===================================
> > This list is hosted by DevelopMentor.  http://www.develop.com
> >
> > View archives and manage your subscription(s) at
> http://discuss.develop.com

> >
> > ===================================
> > This list is hosted by DevelopMentor(r)  http://www.develop.com
> >
> > View archives and manage your subscription(s) at
> http://discuss.develop.com

> >
>
> ===================================
> This list is hosted by DevelopMentorR  http://www.develop.com
>
> View archives and manage your subscription(s) at http://discuss.develop.com

>
> ===================================
> This list is hosted by DevelopMentor(r)  http://www.develop.com
>
> View archives and manage your subscription(s) at http://discuss.develop.com

>

===================================
This list is hosted by DevelopMentorŪ  http://www.develop.com

View archives and manage your subscription(s) at http://discuss.develop.com