public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, mikuback@linux.microsoft.com
Subject: Re: [edk2-devel] CodeQL Analysis in edk2
Date: Wed, 15 Nov 2023 13:00:02 +0100	[thread overview]
Message-ID: <956d6718-41a0-9791-cca6-776376b6b046@redhat.com> (raw)
In-Reply-To: <80681e4d-e438-4d2e-be4f-5268920f6211@linux.microsoft.com>

On 11/15/23 01:35, Michael Kubacki wrote:
> On 11/13/2023 8:42 AM, Laszlo Ersek wrote:
>> sorry, unfinished thought:
>>
>> On 11/13/23 14:39, Laszlo Ersek wrote:
>>
>>> - the "sarif emacs" output seems a bit broken, actually, so it's not
>>> usable. Consider the following entry from the original JSON file:
>>>
>>>      }, {
>>>        "ruleId" : "cpp/missing-null-test",
>>>        "ruleIndex" : 0,
>>>        "rule" : {
>>>          "id" : "cpp/missing-null-test",
>>>          "index" : 0
>>>        },
>>>        "message" : {
>>>          "text" : "Value may be null; it should be checked before
>>> dereferencing."
>>>        },
>>>        "locations" : [ {
>>>          "physicalLocation" : {
>>>            "artifactLocation" : {
>>>              "uri" :
>>> "MdeModulePkg/Application/UiApp/FrontPageCustomizedUiSupport.c",
>>>              "uriBaseId" : "%SRCROOT%",
>>>              "index" : 0
>>>            },
>>>            "region" : {
>>>              "startLine" : 355,
>>>              "startColumn" : 48,
>>>              "endColumn" : 52
>>>            }
>>>          }
>>>        } ],
>>>        "partialFingerprints" : {
>>>          "primaryLocationLineHash" : "f374f6e6dfc92010:1",
>>>          "primaryLocationStartColumnFingerprint" : "43"
>>>        }
>>>      }, {
>>>
>>> In the "emacs" output, it appears as:
>>>
>>> --------
>>> ModulePkg/Application/UiApp/FrontPageCustomizedUiSupport.c:355:
>>> cpp/missing-null-test Value may be null; it should be checked before
>>> dereferencing.
>>> --------
>>>
>>> Note that the first three characters, "Mde" of "Mde" are lost.
>>
>> I meant '"Mde" of "ModulePkg"'.
>>
> I was able to reproduce this with sarif-tools version 2.0.0.
> 
> It impacted other commands like "html" as well.
> 
> Applying the "--no-autotrim" option appears to leave the path alone. Can
> you please let me know if that works for you?

Yes, it does!

Thanks!
Laszlo

> 
> Also, yes, I can add this to the CodeQL GitHub workflow.
> 
>>>
>>> This issue (first three chars cut) affects all other pathnames in the
>>> emacs output too.
>>
> 
> 
> 
> 
> 



-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#111266): https://edk2.groups.io/g/devel/message/111266
Mute This Topic: https://groups.io/mt/102444916/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/leave/12367111/7686176/1913456212/xyzzy [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



  reply	other threads:[~2023-11-15 12:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-07 15:43 [edk2-devel] CodeQL Analysis in edk2 Michael Kubacki
2023-11-13 13:39 ` Laszlo Ersek
2023-11-13 13:42   ` Laszlo Ersek
2023-11-15  0:35     ` Michael Kubacki
2023-11-15 12:00       ` Laszlo Ersek [this message]
2024-02-27 11:39 ` Gerd Hoffmann
2024-02-27 16:04   ` Michael Kubacki
2024-02-28  3:43     ` Laszlo Ersek
2024-02-28  3:55       ` Michael Kubacki
2024-02-28 11:29     ` Gerd Hoffmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=956d6718-41a0-9791-cca6-776376b6b046@redhat.com \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox