similar to: [ANNOUNCE] xcalc 1.0.7

xcalc is a scientific calculator X11 client that can emulate a TI-30 or an HP-10C. This minor maintenance release includes a couple years worth of build improvements, code cleanups, and bug fixes. Alan Coopersmith (9): Remove unused min & max macros from math.c Replace sprintf & strcpy calls with snprintf & strlcpy Remove redundant redeclaration of ‘factorial’

This release adds base conversion (decimal, octal, hexadecimal), bitwise ops (and, or, xor, not, shift left/right, truncate), and a modulo operator to the default TI (infix, i.e. not RPN/postfix) calculator mode. It also binds the Return key to the "=" button. Thanks to Tim Hentenaar for contributing this feature. Alan Coopersmith (5): Add bitwise ops and base conversion

fedora comes with 1.75 so I used that. I also used some additional flags: cppcheck --enable=all --inconclusive --std=posix --force On Wed, Jan 18, 2017 at 11:36 PM, Erik de Castro Lopo <mle+la at mega-nerd.com> wrote: > Rosen Penev wrote: > >> src/libFLAC/bitreader.c | 4 ++-- >> src/libFLAC/bitwriter.c | 4 ++-- >> src/plugin_xmms/plugin.c |

Hi Chris, et. al, I''ve recently come across cppcheck (static analyser for C code) and ran it on the current btrfs directory from Linus''s repo and it''s reported the following potential issues: linux-2.6$ cppcheck -q fs/btrfs/ [fs/btrfs/compression.c:343]: (error) Data is allocated but not initialized: cb [fs/btrfs/compression.c:583]: (error) Data is allocated but not

The Wine development release 2.19 is now available. What's new in this release (see below for details): - Support for 32-bit float audio on Android. - Named pipes now fully handled by the Wine server. - Support for a new Microsoft root certificate. - More transform fixes in GdiPlus. - Some heap allocation optimizations. - Various bug fixes. The source is available from the

The Wine development release 1.7.30 is now available. What's new in this release (see below for details): - More support for fonts in DirectWrite. - Improved ATL thunk support. - A few more C runtime functions. - Regedit import/export fixes. - Various bug fixes. The source is available from the following locations: http://prdownloads.sourceforge.net/wine/wine-1.7.30.tar.bz2

Hello there, I just ran the sourceforge tool cppcheck over the source code of the new Linux kernel 2.6.32.4 It said 1. [./btrfs/free-space-cache.c:600]: (style) Redundant condition. It is safe to deallocate a NULL pointer The source code is                 if (info->bitmap)                         kfree(info->bitmap); I agree with cppcheck. Suggest delete the if test. 2.

Hi, Gene Cumm wrote: > > 3) It feels like this is a moving target where gcc keeps changing and > > different results get reported. Do we have indications that different versions of gcc5 cause different behavior on the same build and boot machines ? Ady wrote: > Since the issue is only present on specific > hardware / firmware, whatever might seem to "solve" the

So, I forwarded the request for highlighting trailing whitespaces to phabricator upstream (https://secure.phabricator.com/T11879), and upstream folks suggest we enable the Lint feature in Arcanist ( https://secure.phabricator.com/book/phabricator/article/arcanist_lint/). This will enforce the check when `arc diff` is run (reviewers wouldn't see the warnings though). There are two linters we

Hi all, There's a typo in the conditional to check the exit condition in ascii_strcasecmp in share/utf8/charset.c. It checks for (!*s1 || !*s1) instead of (!*s1 || !*s2). Attached patch fixes this. Note that the typo did not affect the result of the function as the loop is exited before changing s1 or s2 anyway. The problem was found by cppcheck which is run automatically on the Debian

Why isn’t it in the LLVM repo? > On Nov 16, 2016, at 7:44 AM, Johannes Doerfert <doerfert at cs.uni-saarland.de> wrote: > > We have a clang format based arcanist linter (and some others) in the > Polly repository. When arcanist is used to create a review, the linter > result is shown online. We also have an arcanist add-on to run the lit > tests and show their result in

The Wine development release 1.7.31 is now available. What's new in this release (see below for details): - New version of the Gecko engine based on Firefox 34. - Support for the Visual Studio 2013 version of the C/C++ runtimes. - More font metrics support in DirectWrite. - Some more Direct2D work. - Various bug fixes. The source is available from the following locations:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 All. Just in then case if anyone is using some old piece of hardware like the ibm x440, I could successfully run xen 4.2.3 on it. I have a working kernel .config and a set of xen boot parameters, along with some tuneups in the x440''s BIOS. The problem was quite complex (irq handling pci bus problems, ethtool magics, etc). Occasionally (once

I just installed R on my 64 bit SUSE Linux system -- I compiled with the default x windows support on.. This may be a newbie question (apologies in advance)-- but how does this show up in X? I have SSH'd in to my box and set my display -- I can run xcalc OK -- but when I hit the R binary it just goes to the command line -- if does not give me an x-window. I suspect I need another

The if() statement always evaluated to true. Detected by "cppcheck", not tested on real hardware. Signed-off-by: Thomas Jarosch <thomas.jarosch at intra2net.com> --- drivers/rhino.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/drivers/rhino.c b/drivers/rhino.c index ca66169..e478bcb 100644 --- a/drivers/rhino.c +++ b/drivers/rhino.c @@ -187,7 +187,7

Hello there, Offending source code is ????? if(? ( BattVoltage> 129 ) || ( BattVoltage < 144 ) ) Maybe swap || for && would be better. This problem I found by using cppcheck. It said [rhino.c:190]: (warning) Logical disjunction always evaluates to true: BattVoltage> 129 || BattVoltage < 144. Regards David Binderman

Credit goes to "cppcheck". Signed-off-by: Thomas Jarosch <thomas.jarosch at intra2net.com> --- drivers/mge-utalk.c | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/drivers/mge-utalk.c b/drivers/mge-utalk.c index c6114c7..616e2ad 100644 --- a/drivers/mge-utalk.c +++ b/drivers/mge-utalk.c @@ -465,7 +465,8 @@ void upsdrv_shutdown(void) { char

Credit goess to "cppcheck" Signed-off-by: Thomas Jarosch <thomas.jarosch at intra2net.com> --- drivers/usb-common.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/drivers/usb-common.c b/drivers/usb-common.c index e51f3cf..e459872 100644 --- a/drivers/usb-common.c +++ b/drivers/usb-common.c @@ -116,7 +116,7 @@ int USBNewExactMatcher(USBDeviceMatcher_t

Thomas Schmitt via Syslinux <syslinux at zytor.com> writes: > My best theory is still that SYSLINUX would have some C code > parts which allow the compilers to produce non-equivalent > machine code. > > I see complaints in the output of cppcheck 1.67, which could > match this criterium. Nice list, thanks! By then way there are known errors in the library code, too, see

Hello there, I just ran the static analysis checker "cppcheck" over the source code of icecast version 2.3.3 Amongst many other things, it said [log.c:301]: (warning) Logical conjunction always evaluates to false: log_id < 0 && log_id>= 25. Source code is ??? if (log_id < 0 && log_id>= LOG_MAXLOGS) ??????? return; Suggest replace && with ||.