From owner-freebsd-ports@freebsd.org Wed May 8 11:45:03 2019 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 97C2915A7DC2 for ; Wed, 8 May 2019 11:45:03 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 371086F710; Wed, 8 May 2019 11:45:03 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1354) id 27B911B2B7; Wed, 8 May 2019 11:45:03 +0000 (UTC) From: Jan Beich To: Andrea Venturoli Cc: Konstantin Belousov , timur@FreeBSD.org, freebsd-ports@freebsd.org Subject: Re: Samba dump (useless) core References: <169305b9-64ea-6305-8ef2-9c11b8c9baf3@netfence.it> <20190508102504.GY2748@kib.kiev.ua> <0eb47166-ddaf-d0ed-7730-91341634c72c@netfence.it> Date: Wed, 08 May 2019 13:44:57 +0200 In-Reply-To: <0eb47166-ddaf-d0ed-7730-91341634c72c@netfence.it> (Andrea Venturoli's message of "Wed, 8 May 2019 12:59:57 +0200") Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-Rspamd-Queue-Id: 371086F710 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.93 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-0.997,0]; NEURAL_HAM_SHORT(-0.93)[-0.934,0]; ASN(0.00)[asn:11403, ipnet:2610:1c1:1::/48, country:US]; NEURAL_HAM_LONG(-1.00)[-0.999,0] X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 May 2019 11:45:03 -0000 Andrea Venturoli writes: > While this sheds some light (seems the whole thing has to do with > trust password change), it shows a stack overflow, not an assert. "stack overflow detected" messages are part of -fstack-protector*. Recently, ports/ default changed to -strong in order to follow base/. https://svnweb.freebsd.org/changeset/ports/499897 > a) how do I get out of this? Remove the other member from the domain > and rejoin? Try and fix the DB (how)? Other? (I understand this would > be a question better answere on Samba list, but we are already here). Try adding either to the port's Makefile: SSP_CFLAGS?= -fstack-protector # XXX -strong crashes in some cases or SSP_UNSAFE= yes # XXX crashes in some cases > b) if there's a stack overflow, isn't that a bug? How can I check it > and report it (to FreeBSD or Samba, once the details can let me > decide) if I cannot get a proper core? > I guess I'd have to look into a way to generate debug info with > Poudriere... what's the proper way to do this? How debugging is implemented is up to port maintainer but the framework provides WITH_DEBUG facility that *usually* allows to get debug symbols. If neither DEBUG port option nor WITH_DEBUG make variable provide symbols then file a bug. https://www.freebsd.org/doc/en/books/porters-handbook/install.html#install-strip In addition to debug symbols try building with -fsanitize=address in order to save time finding a place where the overflow occurs.