On Sun, Oct 10, 2021 at 11:09 PM wrote:
> Hello,
>
> when executing a script with ash from busybox in the shebang then the command
> name will contain "sh" instead of the name of the script as expected.
Can't reproduce: I see script name in comm field, not "sh" or "ash":
$ cat comm.tests
{
Hello,
when executing a script with ash from busybox in the shebang then the command name will contain
"sh" instead of the name of the script as expected. This means you can't use "ps -C
On Sun, Oct 10, 2021 at 10:28 AM Bernhard Reutner-Fischer
wrote:
>
> Fixes the following -fanalyzer warning with at least gcc-12.
> Ok for trunk?
Yes please
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
Fixes the following -fanalyzer warning with at least gcc-12.
Ok for trunk?
PS: nowadays our self initializations might do more harm than good,
might even hinder optimizations down the pipe. We should maybe revisit these.
gcc -Wp,-MD,util-linux/.chrt.o.d -std=gnu99 -Iinclude -Ilibbb -include
warning: use of uninitialized value ‘priority’ [CWE-457]
[-Wanalyzer-use-of-uninitialized-value]
chrt_main499 496 -3
--
(add/remove: 0/0 grow/shrink: 0/1 up/down:
