access violation vcl260.pbl

[nicolas fachinetti 0]

Hi,

I have an application who used delphi (i am not the developper of this app)

I have a problem when I am in remote app, on windows 2016 (in MSTSC no problem), sorry it's in french 

It only appears after a period of inactivity, from about 30.45 minutes.
Of course no GPO / Local policy or any configuration on the remote collection regarding time out
1st question: are there any logs specific to deplhi or embarcadero? 
2nd : Does this speak to anyone? 
Sorry for the lack of information 

[Remy Lebeau 1396]

59 minutes ago, nicolas fachinetti said:

I have an application who used delphi (i am not the developper of this app)

The app doesn't use Delphi, it is written in Delphi.  In any case, as an end user of the app, not its developer, you are not going to be able to diagnose that error.  You need to contact the developer to troubleshoot.

59 minutes ago, nicolas fachinetti said:

 

It only appears after a period of inactivity, from about 30.45 minutes.

Offhand, I would guess that a nil pointer is being accessed.  That is likely to be a bug in the app.  Only the developer will be able to find out for sure.

59 minutes ago, nicolas fachinetti said:

are there any logs specific to deplhi or embarcadero? 

No.  The app would be responsible for creating its own logs.

 

[FPiette 383]

You need to run the program under Delphi debugger and for that you need the source code and a Delphi license.

You'd better ask the developer...

[aehimself 396]

On 3/24/2022 at 4:56 PM, Remy Lebeau said:

Offhand, I would guess that a nil pointer is being accessed.

This is really interesting, since it's in VCL260.bpl...? Whenever I made these mistakes the AV always pointed to the executable (or .dll), rarely (or never) to a Delphi internal.

In case it's true, how exactly this can happen?

[David Heffernan 2345]

1 hour ago, aehimself said:

This is really interesting, since it's in VCL260.bpl...? Whenever I made these mistakes the AV always pointed to the executable (or .dll), rarely (or never) to a Delphi internal.

This can easily happen. It's really common. Programming mistake in the app manifests as an exception raised in vcl code. Nothing interesting to see here.