New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Favourites Mode #1366

Open

KrahJohlito wants to merge 2 commits into ps2homebrew:master from KrahJohlito:ftest

Open

Favourites Mode #1366

scroll dia windows if items exceed screen height

Codacy Production / Codacy Static Code Analysis required action Nov 29, 2024 in 0s

5 new issues (0 max.) of at least minor severity.

Here is an overview of what got changed by this pull request:

Issues
======
- Added 5
           

Clones added
============
- src/menusys.c  2

See the complete overview on Codacy

Annotations

Check notice on line 229 in src/favsupport.c

codacy-production / Codacy Static Code Analysis

src/favsupport.c#L229

On some systems (though not Linux-based systems) an attempt to free() results from memalign() may fail. This may, on a few systems, be exploitable.  Also note that memalign() may not check that the boundary parameter is correct (CWE-676).  Use posix_memalign instead (defined in POSIX's 1003.1d).  Don't switch to valloc(); it is marked as obsolete in BSD 4.3, as legacy in SUSv2, and is no longer defined in SUSv3.  In some cases, malloc()'s alignment may be sufficient.

Check notice on line 235 in src/favsupport.c

codacy-production / Codacy Static Code Analysis

src/favsupport.c#L235

On some systems (though not Linux-based systems) an attempt to free() results from memalign() may fail. This may, on a few systems, be exploitable.  Also note that memalign() may not check that the boundary parameter is correct (CWE-676).  Use posix_memalign instead (defined in POSIX's 1003.1d).  Don't switch to valloc(); it is marked as obsolete in BSD 4.3, as legacy in SUSv2, and is no longer defined in SUSv3.  In some cases, malloc()'s alignment may be sufficient.

Check notice on line 272 in src/favsupport.c

codacy-production / Codacy Static Code Analysis

src/favsupport.c#L272

On some systems (though not Linux-based systems) an attempt to free() results from memalign() may fail. This may, on a few systems, be exploitable.  Also note that memalign() may not check that the boundary parameter is correct (CWE-676).  Use posix_memalign instead (defined in POSIX's 1003.1d).  Don't switch to valloc(); it is marked as obsolete in BSD 4.3, as legacy in SUSv2, and is no longer defined in SUSv3.  In some cases, malloc()'s alignment may be sufficient.

Check notice on line 303 in src/favsupport.c

codacy-production / Codacy Static Code Analysis

src/favsupport.c#L303

On some systems (though not Linux-based systems) an attempt to free() results from memalign() may fail. This may, on a few systems, be exploitable.  Also note that memalign() may not check that the boundary parameter is correct (CWE-676).  Use posix_memalign instead (defined in POSIX's 1003.1d).  Don't switch to valloc(); it is marked as obsolete in BSD 4.3, as legacy in SUSv2, and is no longer defined in SUSv3.  In some cases, malloc()'s alignment may be sufficient.

Check notice on line 319 in src/favsupport.c

codacy-production / Codacy Static Code Analysis

src/favsupport.c#L319

On some systems (though not Linux-based systems) an attempt to free() results from memalign() may fail. This may, on a few systems, be exploitable.  Also note that memalign() may not check that the boundary parameter is correct (CWE-676).  Use posix_memalign instead (defined in POSIX's 1003.1d).  Don't switch to valloc(); it is marked as obsolete in BSD 4.3, as legacy in SUSv2, and is no longer defined in SUSv3.  In some cases, malloc()'s alignment may be sufficient.

View more details on Codacy Production