And now integrate it into TThread.NameThreadForDebugging and we have it working crossplatform
QuoteAnd 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.
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.
Quote from: GetMem on January 12, 2018, 04:16:57 pmLooks 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.
@ThaddyThe 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.
But it's not build during build of fpc. What do i have to do to make it build during fpc build?
10:00 CET tomorrow morning
Quote from: Thaddy on January 12, 2018, 10:07:01 pm10:00 CET tomorrow morning Good morning Thaddy, did you test it?