debugging log engine build request

[Bernard Devlin]

No, unfortunately there is no clear pattern.  I'm definitely not doing a lot
of work with images (barely an image in any of my work).  The crashes on
Windows mostly happened over a 3 month period using mostly one stack (and
its substacks).  As I'm not prepared for that work to be viewed by others
(confidentiality issues), I cannot send that stack to Runrev.  At the
beginning of August I sent the Windows crash reports for July to Runrev, but
they were inconclusive.

The Linux crashes last week are on a totally new and unrelated project.
 Hence my suggestion for this enhancement to the engine.

As I've seen how large my message log can get in a matter of hours (despite
them being in a condensed format that's about 10-20% of verboseLog.txt), I
doubt that the Windows crash logs contain a replay log.
Bernard
On Mon, Sep 29, 2008 at 11:48 PM, J. Landman Gay
<jacque at hyperactivesw.com>wrote:

> Are you by chance working a lot with images? I had a severe series of
> crashes in a current project on both 2.9 and 3.0 which turned out to be
> image-related, particularly when manipulating large images (there's a bug
> report about that.) I sent the team my stack and it blew up for them on
> demand. I have a scripted work-around for my particular situation.
>
> I've forgotten if you said you sent them your stack, but I've found that's
> the most reliable way to get things fixed, especially if the crash log is
> inconclusive.
>
> --
> Jacqueline Landman Gay         |     jacque at hyperactivesw.com
>