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
> >>
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
Windows represents exception codes as an unsigned int. The error -1073741819 is
actually0xC005.
This represents some form of access violation, usually associated with
trying to write to freed memory,double freeing memory etc. If the stack
is involved/corrupted then a trackback and useful
Isn't that negative number 0xC005 in hex? If that's the case, it's an
Access Violation and not Disk Full.
Jeff.
On Wed, May 15, 2019 at 11:44 AM James Richters <
ja...@productionautomation.net> wrote:
> It's a simple single thread console app. I found my problem... years
> ago I
It's a simple single thread console app. I found my problem... years ago I
implemented a batch file to run my program in the test environment to help be
with debugging... and what it does is redirect the errors to a file so that if
flashed by real quick, I would be able to just look at the
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
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
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
Maybe close out that bug then?
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
