Re: [fpc-pascal] unexpected termination with no errors

2019-05-16 Thread James Richters
' Subject: Re: [fpc-pascal] unexpected termination with no errors Once I fixed my batch file I am getting exactly this: An unhandled exception occurred at $004E4B4C: EInOutError: Disk Full $004E4B4C GETDATA, line 19078 of pastep.pas $004E9695 GETAFILE, line 19997 of pastep.pas

Re: [fpc-pascal] unexpected termination with no errors

2019-05-16 Thread James Richters
go. James From: fpc-pascal On Behalf Of Gary Doades Sent: Wednesday, May 15, 2019 12:11 PM To: fpc-pascal@lists.freepascal.org Subject: Re: [fpc-pascal] unexpected termination with no errors Windows represents exception codes as an unsigned int. The error -1073741819 is actually

Re: [fpc-pascal] unexpected termination with no errors

2019-05-16 Thread Michael Van Canneyt
On Thu, 16 May 2019, Sven Barth via fpc-pascal wrote: Karoly Balogh (Charlie/SGR) schrieb am Mi., 15. Mai 2019, 18:40: Hi, On Wed, 15 May 2019, Sven Barth via fpc-pascal wrote: (Sidenote: I've been pondering for a while if I should report this as a bug. I think the RTL should put a

Re: [fpc-pascal] unexpected termination with no errors

2019-05-15 Thread Sven Barth via fpc-pascal
Karoly Balogh (Charlie/SGR) schrieb am Mi., 15. Mai 2019, 18:40: > Hi, > > On Wed, 15 May 2019, Sven Barth via fpc-pascal wrote: > > >> (Sidenote: I've been pondering for a while if I should report this as a > >> bug. I think the RTL should put a try-except around there, to show a > >>

Re: [fpc-pascal] unexpected termination with no errors

2019-05-15 Thread Karoly Balogh (Charlie/SGR)
Hi, On Wed, 15 May 2019, Sven Barth via fpc-pascal wrote: >> (Sidenote: I've been pondering for a while if I should report this as a >> bug. I think the RTL should put a try-except around there, to show a >> stacktrace on unhandled exceptions, just like the main thread dying >> does, but who

Re: [fpc-pascal] unexpected termination with no errors

2019-05-15 Thread Gary Doades
they could be negative, but I'm curious why this strange errorlevel. Jim -Original Message- From: fpc-pascal On Behalf Of Karoly Balogh (Charlie/SGR) Sent: Wednesday, May 15, 2019 9:17 AM To: FPC-Pascal users discussions Subject: Re: [fpc-pascal] unexpected termination with no errors Hi

Re: [fpc-pascal] unexpected termination with no errors

2019-05-15 Thread DaWorm
to treat anything less than > zero as an error. so it doesn't really matter, I just didn't know they > could be negative, but I'm curious why this strange errorlevel. > > Jim > > > -Original Message- > From: fpc-pascal On Behalf Of > Karoly Balogh (C

Re: [fpc-pascal] unexpected termination with no errors

2019-05-15 Thread James Richters
Subject: Re: [fpc-pascal] unexpected termination with no errors Hi, On Wed, 15 May 2019, James Richters wrote: > Has anyone encountered anything like this before or know how I can > make sure I always get the maximum amount of debugging info when my > program crashes? Is it a subthr

Re: [fpc-pascal] unexpected termination with no errors

2019-05-15 Thread Sven Barth via fpc-pascal
Karoly Balogh (Charlie/SGR) schrieb am Mi., 15. Mai 2019, 15:25: > Hi, > > On Wed, 15 May 2019, James Richters wrote: > > > Has anyone encountered anything like this before or know how I can make > > sure I always get the maximum amount of debugging info when my program > > crashes? > > Is it a

Re: [fpc-pascal] unexpected termination with no errors

2019-05-15 Thread Karoly Balogh (Charlie/SGR)
Hi, On Wed, 15 May 2019, James Richters wrote: > Has anyone encountered anything like this before or know how I can make > sure I always get the maximum amount of debugging info when my program > crashes? Is it a subthreaded app? The only case when I noticed something similar (under Linux

[fpc-pascal] unexpected termination with no errors

2019-05-15 Thread James Richters
A program I have been working on for years has suddenly developed a bug in it and at a certain point, it is just terminating and not giving me any runtime errors or any error of any kind. It's just running running... running... then BAM - GONE, no explanation%errorlevel% is