dcb314

> Not implementing the SECTION command breaks (m)any usecases that involve building firmware images for >embedded systems. Quite possibly. I checked all of the more than 7,000 packages in Fedora...

>I am assuming that your compiler or whatever tool you are using to detect this error didn't find any > other such problems in the code, which is at least...

Some warnings from the compiler: src/request.c:993:77: warning: '%s' directive output may be truncated writing up to 64 bytes into a region of size between 17 and 144 [-Wformat-truncation=] src/request.c:1059:74: warning:...

gcc flag -Wformat-signedness will help with the last one. I used static analyser cppcheck, available from sourceforge. I recommend it for all C/C++ code.

>Though in this case it is not an error. Surprising. There looks to me to be an embedded assignment to ww[i].len near the end of the list, and a use...

clang, a C++ compiler, with flag -Wall.

Doubtful. I just find the bugs, I don't fix them. If you want to fix it, go ahead.

Thanks for your offer. I don't do pull requests. There were a bunch more of the same warning in the package. 3 fedora/pass297/20220820/librealsense.spec.out:/home/dcb36/rpmbuild/BUILD/librealsense-2.40.0/common/opengl3.cpp:599:21: warning: moving a local object in a...

The warning has recently been enhanced in development versions of gcc. The most recently released version of gcc (12.2) might produce some of these warnings.

>This one, however, I must assert that I find absolutely nothing wrong with the statement. Then you need to understand C better. Incrementing and writing to a variable between sequence...