mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[PR #5134] [MERGED] fzenity: fix dead store #5373
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#5373
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/netblue30/firejail/pull/5134
Author: @kmk3
Created: 5/7/2022
Status: ✅ Merged
Merged: 5/10/2022
Merged by: @kmk3
Base:
master← Head:fix-fzenity-deadstore📝 Commits (1)
bba57f4fzenity: fix dead store📊 Changes
1 file changed (+1 additions, -1 deletions)
View changed files
📝
src/fzenity/main.c(+1 -1)📄 Description
As caught by the Clang Static Analyzer:
The above increment is a no-op, as it is equivalent to
return ptr; ptr++;.For it to make any difference, the prefix increment operator would have
to be used in place of the postfix one:
Which would be equivalent to
++ptr; return ptr;.But in order to fix the warning (and CI) while avoiding to change the
current behavior, just remove the operator instead.
Added on commit
1cdfa6f95("more on firecfg --guide: fzenity",2022-04-25).
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.