From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 6004339DDF20; Thu, 8 Dec 2022 08:52:15 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6004339DDF20 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1670489535; bh=x3HeozaCbnzKX+sIFMjE42Y0eoHKH8XPclz9zZDNevo=; h=From:To:Subject:Date:In-Reply-To:References:From; b=YoA1w+Zh9Lq8vuhYBzdCSnkTLQ1mDFKrZs2cYAboTZQdoRoEadq4lZ5CfrWulL94c wVbdvXdsImkHPIAZ+Nlti5TY4gg+heK9xLGHoP+HOXcKSs1NgFoAebd//EK/iVYcoj mlj0SEstsGpknKYlMC9RWkp9bxCDRyovXdizH8rU= From: "mliska at suse dot cz" To: glibc-bugs@sourceware.org Subject: [Bug manual/28998] Document -D_FORTIFY_SOURCE Date: Thu, 08 Dec 2022 08:52:14 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: manual X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mliska at suse dot cz X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: everconfirmed bug_status cf_reconfirmed_on Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D28998 Martin Liska changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Last reconfirmed| |2022-12-08 --- Comment #6 from Martin Liska --- (In reply to Byron Stanoszek from comment #5) > I too am looking for documentation on this feature. More specifically, wh= at > is the action of the program when the check fails? abort is called. > Does it act like a failed > assert() and call abort()? Is there a way to catch the exception like one > would catch SIGSEGV using a signal handler? Likely not, Siddhesh, please correct me if I'm wrong. > Thanks. Anyway, the documentation should be really improved and taken to GCC compil= er as well. --=20 You are receiving this mail because: You are on the CC list for the bug.=