Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Possible issue: Systemtime vs. Filetime
See original GitHub issueI was referring to your library to verify our own implementation of the GetExtendedTcpTable function, and noticed a potential bug here. Microsoft says the liCreateTimestamp member is a SYSTEMTIME. And as I read it, SYSTEMTIME is time since system boot, while FILETIME is absolute time (irrespective of boot etc.).
I think this member should be a SYSTEMTIME, as to not lead any users to think it’s a FILETIME.
See: https://docs.microsoft.com/en-us/windows/win32/api/tcpmib/ns-tcpmib-mib_tcprow_owner_module
Issue Analytics
- State:
- Created 3 years ago
- Comments:13 (8 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I have updated the comments for those fields and have submitted a PR to Microsoft to change their documentation as well.
Well, the changes you asked me to make (from FILETIME to SYSTEMTIME) did, in fact, break the structure layout. I’m testing now to determine how MS reads that value to get to a time. More to come shortly.