Npcap: use Event Tracing (Windows) instead of writing debug logs to file
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.6k
- Forks
- 592
- PR merge metrics
- No merged PRs in 30d
Description
ETW could be used instead of our TRACE_PRINT* functions. Logging to file like we do involves opening, appending, and closing the log file every time, which has big performance impact. If we did this, then we do not need to solve nmap/nmap#1081.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked ETW documentation and tracing the existing TRACE_PRINT* functions. Determine how the current file logging is performed and how ETW would replace it without reopening the log for every message. Done means debug logging uses Windows Event Tracing and the nmap/nmap#1081 issue is no longer needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100