microsoft / microsoft/CLOG

SKIPPED:BUG:MISSINGARG in MsQuic Logs

Open
#45 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug decode
Dominant language
C#
Stars
36
Forks
15
Avg merge
1d 5m
Merged PRs (30d)
1

Description

I was just looking at a log generated from the MsQuic CI and I found this line (for an assert):

[0][][04:09:46.617630][ lib] ASSERT, 421:"/home/vsts/work/1/s/src/platform/platform_linux.c"<SKIPPED:BUG:MISSINGARG:arg4:ANSI_String>.

This maps to the following code:

void
QuicPlatformLogAssert(
    _In_z_ const char* File,
    _In_ int Line,
    _In_z_ const char* Expr
    )
{
    QuicTraceEvent(
        LibraryAssert,
        "[ lib] ASSERT, %u:%s - %s.",
        (uint32_t)Line,
        File,
        Expr);
}

That is triggered by this macro:

#define QUIC_FRE_ASSERT(exp) ((exp) ? (void)0 : (QuicPlatformLogAssert(__FILE__, __LINE__, #exp), quic_bugcheck()));

I don't know why clog would claim the arg is missing. I suspect a CLOG bug. The artifacts can be found here (for now): https://dev.azure.com/ms/msquic/_build/results?buildId=99107&view=artifacts&type=publishedArtifacts

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the provided MsQuic log artifact and the QuicPlatformLogAssert function and QUIC_FRE_ASSERT macro, then trace how CLOG processes this printf-style event description. Compare the generated assertion output with its three arguments; done means the log no longer reports SKIPPED:BUG:MISSINGARG for this event.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, csharp
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.