Re: [Oorexx-devel] Intermittent failure

2011-06-12 Thread Mike Cowlishaw
Not sure what you mean by 'attach to process'? With the menu Debug/Attach to process you can select a running process from a list, and when a breakpoint is reached, the process is stopped on this breakpoint. In your case, when the exception is triggered, you should have the call stack in t

Re: [Oorexx-devel] Intermittent failure

2011-06-12 Thread Jean-Louis Faucher
> > > Not sure what you mean by 'attach to process'? > > > With the menu Debug/Attach to process you can select a running process from a list, and when a breakpoint is reached, the process is stopped on this breakpoint. In your case, when the exception is triggered, you should have the call stack

Re: [Oorexx-devel] Intermittent failure

2011-06-12 Thread Mike Cowlishaw
Interesting .. I have Express 2008 and it doesn't seem to have that. Time to upgrade thanks! Mike I remember that Express 2008 had the attach to process... So don't upgrade only for that :-) Not sure what you mean by 'attach to process'? -

Re: [Oorexx-devel] Intermittent failure

2011-06-12 Thread Jean-Louis Faucher
> > > Interesting .. I have Express 2008 and it doesn't seem to have that. Time > to upgrade thanks! > > Mike > > I remember that Express 2008 had the attach to process... So don't upgrade only for that :-) Jean-Louis

Re: [Oorexx-devel] Intermittent failure

2011-06-12 Thread Mike Cowlishaw
Hi Mike 2011/6/12 Mike Cowlishaw Unfortunately the Windows C++ I have doesn't seem to have the 'start debugger on exception' feature that previous versions had :-(. But it might help having the symbols etc. That reminds me a similar problem I had with Visual C++ 2010 Express : no attach

Re: [Oorexx-devel] Intermittent failure

2011-06-12 Thread Jean-Louis Faucher
Hi Mike 2011/6/12 Mike Cowlishaw > Unfortunately the Windows C++ I have doesn't seem to have the 'start > debugger on > exception' feature that previous versions had :-(. But it might help > having the > symbols etc. > That reminds me a similar problem I had with Visual C++ 2010 Express : no a

Re: [Oorexx-devel] Intermittent failure

2011-06-11 Thread Mike Cowlishaw
> > > Before this gets too cold .. any luck in recreating map/determining > > point of failure? > > Hi Mike, > > I just got most of my system rebuilt and can build from the > 4.1.0 release source. I'll get you the map for the build. Actually map of itself not terribly useful, as I don't ha

Re: [Oorexx-devel] Intermittent failure

2011-06-11 Thread Mike Cowlishaw
> -Original Message- > From: Mark Miesfeld [mailto:miesf...@gmail.com] > Sent: 11 June 2011 19:40 > To: Open Object Rexx Developer Mailing List > Subject: Re: [Oorexx-devel] Intermittent failure > > On Sat, Jun 11, 2011 at 11:15 AM, Mike Cowlishaw > wrote:

Re: [Oorexx-devel] Intermittent failure

2011-06-11 Thread Mark Miesfeld
On Sat, Jun 11, 2011 at 11:15 AM, Mike Cowlishaw wrote: > Before this gets too cold .. any luck in recreating map/determining point of > failure? Hi Mike, I just got most of my system rebuilt and can build from the 4.1.0 release source. I'll get you the map for the build. I could build you a

Re: [Oorexx-devel] Intermittent failure

2011-06-11 Thread Mike Cowlishaw
Before this gets too cold .. any luck in recreating map/determining point of failure? Mike > -Original Message- > From: Mark Miesfeld [mailto:miesf...@gmail.com] > Sent: 30 May 2011 18:43 > To: Open Object Rexx Developer Mailing List > Subject: Re: [Oorexx-devel] Inter

Re: [Oorexx-devel] Intermittent failure

2011-05-30 Thread Mike Cowlishaw
> Yeah 0xC005 is a memory access violation. Along with a > NULL pointer, deferencing a number that doesn't point to > valid memory is very common. > > Unfortunately, the hard disk that 4.1.0 was built on crashed > on me, so the map is in the ether somewhere. > > As soon as I get things

Re: [Oorexx-devel] Intermittent failure

2011-05-30 Thread Mark Miesfeld
On Mon, May 30, 2011 at 3:15 AM, Mike Cowlishaw wrote: > Hmm, more likely accessing something witha NULL pointer, I'd have thought. > Anyway, someone who has the map for that build should be able to have a good > guess from the code that is being executed, I'm hoping. Hi Mike, Yeah 0xC005 i

Re: [Oorexx-devel] Intermittent failure

2011-05-30 Thread Mike Cowlishaw
com] Sent: 30 May 2011 09:35 To: Open Object Rexx Developer Mailing List Subject: Re: [Oorexx-devel] Intermittent failure C05 is stack overflow through unbounded looping most of the time René Vincent Jansen On 30 mei 2011, at 09:55, "Mike Cowlishaw" wrote: I'm ha

Re: [Oorexx-devel] Intermittent failure

2011-05-30 Thread René Vincent Jansen
C05 is stack overflow through unbounded looping most of the time René Vincent Jansen On 30 mei 2011, at 09:55, "Mike Cowlishaw" wrote: > I'm having a rare failure in my (multi-threaded) web server. The fault could > well be mine, but as the failure occurs in rexx.dll I'm having trouble

[Oorexx-devel] Intermittent failure

2011-05-30 Thread Mike Cowlishaw
I'm having a rare failure in my (multi-threaded) web server. The fault could well be mine, but as the failure occurs in rexx.dll I'm having trouble getting a handle on it. Any pointers as to what might be causing it would be really helpful. The details: Exception: 0xC005 Location: o