Re: debugging log engine build request
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 [EMAIL PROTECTED]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 | [EMAIL PROTECTED] ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
debugging log engine build request
Since I've been having unpredictable but frequent crashes of Revolution 2.9 on Vista for the past 4 months, and now daily crashes of Revolution 3.0 on Vista and Linux, I've entered an enhancement request that the engine be modified to include a debug-logging facility (logging messages, property changes, and function calls). If anyone is interested in adding their suggestions or doubts about this enhancement, the bug reference number is 7237 (http://quality.runrev.com/qacenter/show_bug.cgi?id=7237). Bernard ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: debugging log engine build request
Dear Bernard, Isn't the verbose log useful for you? To turn verbose logging on and off easily, you can download my Verbose Log plugin from RevOnline (user name Mark). -- Best regards, Mark Schonewille Economy-x-Talk Consulting and Software Engineering http://economy-x-talk.com http://www.salery.biz Dutch forum: http://runrev.info/rrforum/ Benefit from our inexpensive hosting services. See http://economy-x-talk.com/server.html for more info. On 29 sep 2008, at 11:18, Bernard Devlin wrote: Since I've been having unpredictable but frequent crashes of Revolution 2.9 on Vista for the past 4 months, and now daily crashes of Revolution 3.0 on Vista and Linux, I've entered an enhancement request that the engine be modified to include a debug-logging facility (logging messages, property changes, and function calls). If anyone is interested in adding their suggestions or doubts about this enhancement, the bug reference number is 7237 (http://quality.runrev.com/qacenter/show_bug.cgi?id=7237). Bernard ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: debugging log engine build request
Hi Mark, I don't know. Before I built my own utility, I mentioned the need for something like this several times (on the improve list and in comments on RQCC). No-one referred me to yours. Can it log changes to properties (such as setting the name of a stack), and calls to in-built functions? If it can't do that, then I think there is still a need for what I've suggested. Mind you, I use your errorLib all the time, so if someone can do it outside the engine, I'm sure you can. I've just found it your stack. I didn't know there was anything called revVerboseDebug. It isn't listed in the dictionary of either 2.9 or 3.0. So it certainly looks like your logging stack will do more, so I probably wasted another day. Bernard On Mon, Sep 29, 2008 at 12:21 PM, Mark Schonewille [EMAIL PROTECTED] wrote: Dear Bernard, Isn't the verbose log useful for you? To turn verbose logging on and off easily, you can download my Verbose Log plugin from RevOnline (user name Mark). -- Best regards, Mark Schonewille ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: debugging log engine build request
Hi Mark, I've had a look at your stack, and I see that it simply a method to switch on this undocumented feature that already exists in Rev. My stack does the same as this existing feature - only my method does not waste so much hard disk space, and will produce a new log file every time Rev is restarted (so that if the same sequence of events causes the crash then the log files that were last modified at the times of the crashes should all end the same way). I'm glad to know my work hasn't a complete waste of time. I do think it should be an engine-level feature, and should probably adopt a more concise logging format. If there is any interest in this let me know and I'll put my stack online. Bernard On Mon, Sep 29, 2008 at 1:26 PM, Bernard Devlin [EMAIL PROTECTED] wrote: Hi Mark, I don't know. Before I built my own utility, I mentioned the need for something like this several times (on the improve list and in comments on RQCC). No-one referred me to yours. Can it log changes to properties (such as setting the name of a stack), and calls to in-built functions? If it can't do that, then I think there is still a need for what I've suggested. Mind you, I use your errorLib all the time, so if someone can do it outside the engine, I'm sure you can. I've just found it your stack. I didn't know there was anything called revVerboseDebug. It isn't listed in the dictionary of either 2.9 or 3.0. So it certainly looks like your logging stack will do more, so I probably wasted another day. Bernard ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: debugging log engine build request
Bernard Devlin wrote: Since I've been having unpredictable but frequent crashes of Revolution 2.9 on Vista for the past 4 months, and now daily crashes of Revolution 3.0 on Vista and Linux, I've entered an enhancement request that the engine be modified to include a debug-logging facility (logging messages, property changes, and function calls). This already exists in the Preferences. In the General pane, look for the popdown called Crash reporting on Windows XP. The default setting is small but you can set it to medium (which is actually pretty large.) The resulting log will not be human-readable, but the engineers can use it to debug your crashes. -- Jacqueline Landman Gay | [EMAIL PROTECTED] HyperActive Software | http://www.hyperactivesw.com ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: debugging log engine build request
I sent a whole series of crash logs through RQCC back in August, and was told they were inconclusive. I assumed these crash logs were actually _Windows_ crash logs not Rev crash logs. I seem to remember some discussion between you and Eric Chatonet where he was reluctant to send them because they were encrypted. I think you talked to the Rev developers who told you they were Visual Studio crash logs. My understanding is that these logs do not even exist in the Linux build at all. If I'm not mistaken then I'm asking for something completely different. I'm asking for something that would be equivalent to a 'replay log', so that the Rev developers could see exactly what was going on inside the engine as the engine changes state before a crash. Bernard On Mon, Sep 29, 2008 at 4:03 PM, J. Landman Gay [EMAIL PROTECTED]wrote: Bernard Devlin wrote: Since I've been having unpredictable but frequent crashes of Revolution 2.9 on Vista for the past 4 months, and now daily crashes of Revolution 3.0 on Vista and Linux, I've entered an enhancement request that the engine be modified to include a debug-logging facility (logging messages, property changes, and function calls). This already exists in the Preferences. In the General pane, look for the popdown called Crash reporting on Windows XP. The default setting is small but you can set it to medium (which is actually pretty large.) The resulting log will not be human-readable, but the engineers can use it to debug your crashes. -- Jacqueline Landman Gay | [EMAIL PROTECTED] HyperActive Software | http://www.hyperactivesw.com ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: debugging log engine build request
Bonsoir Bernard, Yes these logs just exist on Win32. I had some prejudice against them, that's true, because these logs are not readable. But I know a bit Mark Waddingham and I'm sure now these logs do not tell to Runrev parts of code or something else that could disclosure any part of your work. Anyway, if you work with Linux, these logs are nor available AFAIK. As for a 'replay log' that would be a panacea, I imagine it would be difficult to set up and probably not understandable for common users (e.g. not acceptable from a marketing point of view) :-) Le 29 sept. 08 à 22:04, Bernard Devlin a écrit : I sent a whole series of crash logs through RQCC back in August, and was told they were inconclusive. I assumed these crash logs were actually _Windows_ crash logs not Rev crash logs. I seem to remember some discussion between you and Eric Chatonet where he was reluctant to send them because they were encrypted. I think you talked to the Rev developers who told you they were Visual Studio crash logs. My understanding is that these logs do not even exist in the Linux build at all. If I'm not mistaken then I'm asking for something completely different. I'm asking for something that would be equivalent to a 'replay log', so that the Rev developers could see exactly what was going on inside the engine as the engine changes state before a crash. Best regards from Paris, Eric Chatonet. Plugins and tutorials for Revolution: http://www.sosmartsoftware.com/ Email: [EMAIL PROTECTED]/ ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: debugging log engine build request
Bernard Devlin wrote: I sent a whole series of crash logs through RQCC back in August, and was told they were inconclusive. I assumed these crash logs were actually _Windows_ crash logs not Rev crash logs. They're Rev crash logs, the actual Windows logs can be accessed from Dr Watson (at least in XP, not sure about Vista.) I believe the Rev crash logs do show the various machine states as Rev executes commands. I seem to remember some discussion between you and Eric Chatonet where he was reluctant to send them because they were encrypted. I think you talked to the Rev developers who told you they were Visual Studio crash logs. My understanding is that these logs do not even exist in the Linux build at all. Right, I don't think there's any logging for Linux. I thought you mentioned that the crash happened on both Windows and Linux though, and I was hoping the Windows logs would give a clue to the problem on both. If I'm not mistaken then I'm asking for something completely different. I'm asking for something that would be equivalent to a 'replay log', so that the Rev developers could see exactly what was going on inside the engine as the engine changes state before a crash. I think that's what the Rev logs do mostly, if you have the software to read them. But if you have any other logging tools, the more the better. Go for it. 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 | [EMAIL PROTECTED] HyperActive Software | http://www.hyperactivesw.com ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
