Re: nginx 1.24 + njs build errors [-Werror=dangling-pointer=] after switch from GCC 12 (Fedora 37) -> GCC13 (Fedora 38)

GCC 13 is not released yet, right? "Real Soon Now (tm)" GCC 13.0.1 Status Report (2023-04-17) https://gcc.gnu.org/pipermail/gcc/2023-April/241140.html It's in the Fedora 38 release, which dropped today: Fedora 38 Released With GNOME 44 Desktop, GCC 13, Many New Features

Re: nginx 1.24 + njs build errors [-Werror=dangling-pointer=] after switch from GCC 12 (Fedora 37) -> GCC13 (Fedora 38)

On 4/18/23 10:26 AM, PGNet Dev wrote: I'm building nginx mainline v1.24 on Fedora. on F37, with gcc 12, gcc --version     gcc (GCC) 12.2.1 20221121 (Red Hat 12.2.1-4)     Copyright (C) 2022 Free Software Foundation, Inc.     This is free software; see the source for

Re: resolver does not work

Hello! On Tue, Apr 18, 2023 at 10:25:09PM +0200, basti wrote: > Hello Maxim, > > that does not work for me. > > root@tower:~# resolvectl query icinga2 > icinga2: 192.168.145.217 -- link: ve-icinga2 > > -- Information acquired via protocol LLMNR/IPv4 in 105.7ms. > -- Data

Re: resolver does not work

Hello Maxim, that does not work for me. root@tower:~# resolvectl query icinga2 icinga2: 192.168.145.217 -- link: ve-icinga2 -- Information acquired via protocol LLMNR/IPv4 in 105.7ms. -- Data is authenticated: no root@tower:~# getent hosts icinga2 192.168.145.217 icinga2

Re: resolver does not work

Hi, On 18/04/2023 13:58, mailingl...@unix-solution.de wrote: Hello, I have a nginx proxy in front of systemd-nspawn containers. The IP's of the containers are dynamic. When I start nginx *after* the  containers it works. When the IP of the container is changed while nginx is running i get a

Re: resolver does not work

Hello! On Tue, Apr 18, 2023 at 02:58:08PM +0200, mailingl...@unix-solution.de wrote: > Hello, > I have a nginx proxy in front of systemd-nspawn containers. > The IP's of the containers are dynamic. > > When I start nginx *after* the  containers it works. > When the IP of the container is

Re: [PATCH 0 of 4] Avoid dead store elimination in GCC 11+

Hello! On Tue, Apr 18, 2023 at 10:50:01AM +0100, Vadim Fedorenko wrote: > On 18.04.2023 02:54, Maxim Dounin wrote: > > Hello! > > > > On Tue, Apr 18, 2023 at 02:07:06AM +0300, Vadim Fedorenko via nginx-devel > > wrote: > > > >> GCC version 11 and newer use more aggressive way to eliminate

Re: resolver does not work

Sorry, my mistake. 1.18.0 debian11 is installed. Am 18.04.23 um 19:21 schrieb A. Schulze via nginx: Am 18.04.23 um 14:58 schrieb mailingl...@unix-solution.de: nginx is 1.1.18 Whats wrong there? released in March 2012 couldn't you use a "not so historic" version? Andreas

Re: ngx_list_free

Hello! On Tue, Apr 18, 2023 at 03:12:08PM +, Yuval Abadi via nginx wrote: > Thanks > > I just need list not queue, Queue is a double-linked list. > And I want to free the whole list , not one node. In nginx, memory allocations use pools, and in most cases you cannot free individual

nginx 1.24 + njs build errors [-Werror=dangling-pointer=] after switch from GCC 12 (Fedora 37) -> GCC13 (Fedora 38)

I'm building nginx mainline v1.24 on Fedora. on F37, with gcc 12, gcc --version gcc (GCC) 12.2.1 20221121 (Red Hat 12.2.1-4) Copyright (C) 2022 Free Software Foundation, Inc. This is free software; see the source for copying conditions.

Re: resolver does not work

Am 18.04.23 um 14:58 schrieb mailingl...@unix-solution.de: nginx is 1.1.18 Whats wrong there? released in March 2012 couldn't you use a "not so historic" version? Andreas ___ nginx mailing list nginx@nginx.org

[nginx] Fixed segfault if regex studies list allocation fails.

details: https://hg.nginx.org/nginx/rev/77d5c662f3d9 branches: changeset: 8163:77d5c662f3d9 user: Maxim Dounin date: Tue Apr 18 06:28:46 2023 +0300 description: Fixed segfault if regex studies list allocation fails. The rcf->studies list is unconditionally accessed by

Re: nginxQuic: зависание соединения и сброс на HTTP/2 протокол

Добрый день, Илья. > On 17 Apr 2023, at 16:09, Илья Шипицин wrote: > > QUIC Interop Runner (seemann.io) - интересно, > что curl не участвует в кросс тестировании curl использует сторонние библиотеки для поддержки http/3. одна из них ngtcp2, и она в интеропе есть.

RE: ngx_list_free

Thanks I just need list not queue, And I want to free the whole list , not one node. -Original Message- From: nginx On Behalf Of Maxim Dounin Sent: Tuesday, 18 April 2023 15:36 To: Yuval Abadi via nginx Subject: Re: ngx_list_free EXTERNAL MAIL: nginx-boun...@nginx.org Hello!

Re: [PATCH 0 of 4] Avoid dead store elimination in GCC 11+

Hello Vladim, On 4/18/23 11:50, Vadim Fedorenko via nginx-devel wrote: > On 18.04.2023 02:54, Maxim Dounin wrote: >> Hello! >> >> On Tue, Apr 18, 2023 at 02:07:06AM +0300, Vadim Fedorenko via nginx-devel >> wrote: >> >>> GCC version 11 and newer use more aggressive way to eliminate dead stores

resolver does not work

Hello, I have a nginx proxy in front of systemd-nspawn containers. The IP's of the containers are dynamic. When I start nginx *after* the  containers it works. When the IP of the container is changed while nginx is running i get a "Bad Gateway" error. The config looks like: server {    

Re: ngx_list_free

Hello! On Tue, Apr 18, 2023 at 06:14:46AM +, Yuval Abadi via nginx wrote: > Ngx_list_t have create api but no free_list api > > Why? > > I wrote my own free_list, is anyone else face this issue? Much like many things in nginx, ngx_list_t structure is an append-only structure, and

Re: [PATCH 0 of 4] Avoid dead store elimination in GCC 11+

On 18.04.2023 02:54, Maxim Dounin wrote: Hello! On Tue, Apr 18, 2023 at 02:07:06AM +0300, Vadim Fedorenko via nginx-devel wrote: GCC version 11 and newer use more aggressive way to eliminate dead stores which ends up removing ngx_memzero() calls in several places. Such optimization affects

ngx_list_free

Hi Ngx_list_t have create api but no free_list api Why? I wrote my own free_list, is anyone else face this issue? ___ nginx mailing list nginx@nginx.org https://mailman.nginx.org/mailman/listinfo/nginx