[PATCH 8/8] tcpdump: Do not use signals and chroot

Update #4650. --- freebsd/contrib/tcpdump/tcpdump.c | 22 -- 1 file changed, 20 insertions(+), 2 deletions(-) diff --git a/freebsd/contrib/tcpdump/tcpdump.c b/freebsd/contrib/tcpdump/tcpdump.c index 73e2e844..5b658412 100644 --- a/freebsd/contrib/tcpdump/tcpdump.c +++ b/freeb

[PATCH 6/8] tcpdump: No loop monitor if reading from file

Update #4650. --- freebsd/contrib/tcpdump/tcpdump.c | 16 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/freebsd/contrib/tcpdump/tcpdump.c b/freebsd/contrib/tcpdump/tcpdump.c index a02fa184..db5c9221 100644 --- a/freebsd/contrib/tcpdump/tcpdump.c +++ b/freebsd/cont

[PATCH 7/8] tcpdump: Ensure loop monitor termination

Update #4650. --- freebsd/contrib/tcpdump/tcpdump.c | 44 --- 1 file changed, 29 insertions(+), 15 deletions(-) diff --git a/freebsd/contrib/tcpdump/tcpdump.c b/freebsd/contrib/tcpdump/tcpdump.c index db5c9221..73e2e844 100644 --- a/freebsd/contrib/tcpdump/tcpdump.c +

[PATCH 5/8] tcpdump: Close pcap dumper at program exit

Update #4650. --- freebsd/contrib/tcpdump/tcpdump.c | 13 + 1 file changed, 13 insertions(+) diff --git a/freebsd/contrib/tcpdump/tcpdump.c b/freebsd/contrib/tcpdump/tcpdump.c index 0438dd37..a02fa184 100644 --- a/freebsd/contrib/tcpdump/tcpdump.c +++ b/freebsd/contrib/tcpdump/tcpdum

[PATCH 1/8] tcpdump01: New test

Update #4650. --- libbsd.py | 1 + testsuite/tcpdump01/test_main.c | 292 2 files changed, 293 insertions(+) create mode 100644 testsuite/tcpdump01/test_main.c diff --git a/libbsd.py b/libbsd.py index 2d3b718d..983f41a1 100644 --- a/libbsd

[PATCH 4/8] tcpdump: Use rtems_task_exit()

Update #4650. --- freebsd/contrib/tcpdump/tcpdump.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/freebsd/contrib/tcpdump/tcpdump.c b/freebsd/contrib/tcpdump/tcpdump.c index 74c878a3..0438dd37 100644 --- a/freebsd/contrib/tcpdump/tcpdump.c +++ b/freebsd/contrib/tcpdump/tcp

[PATCH 2/8] Add program destructor support

Update #4650. --- rtemsbsd/include/machine/rtems-bsd-program.h | 6 +++ rtemsbsd/rtems/program-internal.h| 7 +++ rtemsbsd/rtems/rtems-program.c | 51 3 files changed, 64 insertions(+) diff --git a/rtemsbsd/include/machine/rtems-bsd-program.h b/rt

[PATCH 3/8] tcpdump: Make loop monitor cooperative

This helps a bit if the fgetc() is non-blocking. Update #4650. --- freebsd/contrib/tcpdump/tcpdump.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/freebsd/contrib/tcpdump/tcpdump.c b/freebsd/contrib/tcpdump/tcpdump.c index b1e7f0d1..74c878a3 100644 --- a/freebsd/contrib/tcpdump/tcpdump.

[PATCH 0/8] tcpdump: Fix dumping to file and reading from file

This patch is for the 5-freebsd-12, 6-freebsd-12, and master branches of libbsd. Sebastian Huber (8): tcpdump01: New test Add program destructor support tcpdump: Make loop monitor cooperative tcpdump: Use rtems_task_exit() tcpdump: Close pcap dumper at program exit tcpdump: No loop mon

Re: Update to GCC 12 for development branch (RTEMS 6)

On 10/5/2022 7:26 pm, Sebastian Huber wrote: > On 10/05/2022 10:28, Chris Johns wrote: >> On 10/5/2022 1:13 am, Sebastian Huber wrote: >>> Hello Karel, >>> >>> On 09/05/2022 17:09, Karel Gardas wrote: I'm just curious is there any reason to use GCC from git (post release version) and not

Re: [PATCH] hexdump-conv.c: Fix gcc 12 compiler warning

On 10/05/2022 13:27, Matthew Joyce wrote: From: Matt Joyce Fixed newly generated compiler warning introduced in the switch to gcc 12. gcc 12 adds the new warning -Warray-compare, which warns agains potentially dubious comparisons between operands of array type. --- cpukit/libmisc/shell/hexdum

[PATCH] hexdump-conv.c: Fix gcc 12 compiler warning

From: Matt Joyce Fixed newly generated compiler warning introduced in the switch to gcc 12. gcc 12 adds the new warning -Warray-compare, which warns agains potentially dubious comparisons between operands of array type. --- cpukit/libmisc/shell/hexdump-conv.c | 2 +- 1 file changed, 1 insertion(

Re: Update to GCC 12 for development branch (RTEMS 6)

On 10/05/2022 10:28, Chris Johns wrote: On 10/5/2022 1:13 am, Sebastian Huber wrote: Hello Karel, On 09/05/2022 17:09, Karel Gardas wrote: I'm just curious is there any reason to use GCC from git (post release version) and not vanilla 12.1 release tarball from gcc.gnu.org? this makes it easie

Re: Update to GCC 12 for development branch (RTEMS 6)

On 10/5/2022 1:13 am, Sebastian Huber wrote: > Hello Karel, > > On 09/05/2022 17:09, Karel Gardas wrote: >> I'm just curious is there any reason to use GCC from git (post release >> version) and not vanilla 12.1 release tarball from gcc.gnu.org? > > this makes it easier to pick up a GCC 12 releas