Is there any way to name my threads for debugging?

[GetMem]

Pascal there is no need for thanks. If the DebuggerIntf idea is not working you can try something else, like sending a message to ThreadDlg window with PostMessage for example.  Unfortunately we are limited by the gdb, a custom debugger would be the ideal solution.

[GetMem]

Hi Pascal,

Please apply the attached patch(LazFiles.zip), then test the attached project(ThreadName.zip). The patch modifies the following files, please do backup before start:
   $(LazarusDir)\components\debuggerintf\dbgintfdebuggerbase.pp
   $(LazarusDir)\debugger\threaddlg.pp
   $(LazarusDir)\ide\debugmanager.pas
With the patch, I also attach the units if you need them. After IDE rebuild, open the project, put a break point in the thread execute method, run the project then press the "Create thread" button.
You should see the thread name as in the attached screenshot. Tested with 64 bit Lazarus too.

regards,
GetMem

[Pascal]

Great 
And now integrate it into TThread.NameThreadForDebugging and we have it working crossplatform

[GetMem]

And now integrate it into TThread.NameThreadForDebugging and we have it working crossplatform

It is cross-platform already. I will ask the core developers if this or a similar solution is accepted in Lazarus. TThread.NameThreadForDebugging is in FPC, adding the name there it's useless because of the gdb.

[Pascal]

And now integrate it into TThread.NameThreadForDebugging and we have it working crossplatform

It is cross-platform already. I will ask the core developers if this or a similar solution is accepted in Lazarus. TThread.NameThreadForDebugging is in FPC, adding the name there it's useless because of the gdb.

Yes, but you can integrate it in fpc and if NameThreadForDebugging is used it'll work. All you need is in fpc.

Edit:
Of cause this is only usefull if it's used with Lazarus.

[Pascal]

Have a look at the attched patch for fpc. It's neither tested nor build so far.

[GetMem]

Have a look at the attched patch for fpc.

Looks good but I seriously doubt it will be accepted by FPC developers. The code is only useful when you debug an application from Lazarus, why should be present in classes.inc? At least this is how I see it.

[Pascal]

Looks good but I seriously doubt it will be accepted by FPC developers. The code is only useful when you debug an application from Lazarus, why should be present in classes.inc? At least this is how I see it.

Yes, but that's another story.

Maybe there could be implemented an interface class for Lazarus which can be instantiated by Lazarus apps and fpc classes use it if assigned.
I'll update the patch and test it.

[Thaddy]

Looks good but I seriously doubt it will be accepted by FPC developers. The code is only useful when you debug an application from Lazarus, why should be present in classes.inc? At least this is how I see it.

Yes, but that's another story.

No it is not: classes unit should be clean. It is the base unit for classes. Basically introducing something like this is a sin.

Maybe there could be implemented an interface class for Lazarus which can be instantiated by Lazarus apps and fpc classes use it if assigned.
I'll update the patch and test it.

The implementation can only be for platform(s) that support it which I count as one (one). So it should be in the windows specific code.

[GetMem]

@Thaddy
The implementation can only be for platform(s) that support it which I count as one (one). So it should be in the windows specific code.

Just apply the patch(see above), then test the project. In theory it should work in every platform. In fact this is a good chance to test it on raspberry pi. Can you please do a quick test?

PS: I already tested on Linux mint and works fine.
PS1: If it's not working then IPC fails on that specific platform. IPC is a built in FPC feature.

[Thaddy]

10:00 CET tomorrow morning 

[Pascal]

I integrated an interface class to fpc and fpc compiles fine with -dFPC_USE_LAZINTF. (See atached patches).

Unit lazintf is placed in /rtl/objpas. But it's not build during build of fpc. What do i have to do to make it build during fpc build?

[GetMem]

But it's not build during build of fpc. What do i have to do to make it build during fpc build?

Try to add lazintf to fpmake from /rtl/.

[Pascal]

10:00 CET tomorrow morning 

Good morning Thaddy, did you test it?

[Pascal]

10:00 CET tomorrow morning 

Good morning Thaddy, did you test it?

Thaddy, did you had a chance to test it?