News for hackers. Stuff that matters.

A comment on O(n^2), again, now in Windows Management Instrumentation. Parent comment

Re:O(n^2), again, now in Windows Management Instrumentation by albertzeyer on Monday December 09, 2019 @11:58AM (#21744180)
For reference, this was the old API: https://docs.microsoft.com/en-us/visualstudio/debugger/how-t...

This was well known, and many applications actually used that. Of course it was very ugly. I don't think it would have been a problem to also rename a given thread multiple times, but not sure.

[ Parent | on HN ]
Re:O(n^2), again, now in Windows Management Instrumentation by jgalar on Monday December 09, 2019 @04:09PM (#21746610)
It's very ugly, but at least it doesn't seem to limit you to 15 characters like on Linux (prctl/pthread_set_name_np).

That limit makes it pretty hard to provide meaningful identifiers in a non-trivial application.

[ Parent | on HN ]
Re:O(n^2), again, now in Windows Management Instrumentation by brucedawson on Monday December 09, 2019 @06:38PM (#21747920)
Funny thing, windbg apparently uses a fixed-size buffer to store the old-style thread names and it must use strncpy to copy them in because if your thread names are long enough then windbg displays the first ~15 characters and then shows garbage, because strncpy doesn't guarantee null-termination.

Harmless I think, but sloppy.

[ Parent | on HN ]