That's cool...but the SMTP server that my app sends through is my own
email account/server (Thanks, Rackspace!) not something provided by the
customer.
But you're correct that it would be dicey in a shutdown scenario. It's
also kind of worthless in a "no internet connection" scenario.
Ah...wading through the memory dump...such fond memories. Actually
though, I've found many errors that have provided exactly the source of
the problem that triggered the error by reading through the memvars.
And, after you do that a few hundred times, you know what to ignore and
what to look for. The pattern never changes...much.
Mike C
-------- Original Message --------
Subject: Re: Indecipherable VFP Error 2115
From: Ken Dibble <[email protected]>
To: [email protected]
Date: 7/31/2013 1:49 PM
At 01:16 PM 7/31/2013 -0500, you wrote:
It might be overkill, but I have an error routine that
a) dumps all memory, open files, etc. to a text file
b) takes a snapshot of the entire screen and saves it to an EMF file
(like a bitmap)
c) then ZIPs it all into one file to send me an email with the ZIP
attached.
In theory, I like the idea of having the system email me. In practice,
it's one more moving part that can fail, because it depends on being
able to communicate with an SMTP server, and that server being able to
send a message--and could be likely to fail during a shutdown
scenario. It is even more likely to fail with my non-in-house
customers, who cannot be depended upon to maintain a functioning email
server and/or internet connection, and whose alleged "IT people" can't
even figure out how to fill in the proper blanks to set up a POP
account in an email client.
I have a pretty good error logging system and I keep adding stuff to
it. I also have a generic text-file-writing facility that can be
called at any time anywhere in the program when needed to do the kind
of instrumentation we've been talking about.
But, having tried to scroll through VFP memory dumps in the past, and
not being able to make head nor tail of them, I've decided to spare
myself that particular aggravation. In a case where something may have
mangled the stack, which this might turn out to be, I don't think the
most relevant memory contents would be dump-able anyway.
Thanks.
Ken Dibble
www.stic-cil.org
[excessive quoting removed by server]
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
