From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 36F523832BA0; Thu, 8 Dec 2022 15:04:31 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 36F523832BA0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1670511871; bh=8rLtnRyxz6iUdGWYwqrC67JXKo+qjFdnNzt/e5Z8OKs=; h=From:To:Subject:Date:In-Reply-To:References:From; b=vJ3iJQJc1ExAscUv+IGWFn07FvAddLI43a2+9fCZacSl0Wgr9uCDkJgwOZ6vWAARO rWQvkDgoC8PfPwGDNevxVg3aHgM/48AltS5upoQ3igkcWjVNzfCfYq1BdMKjlXdZ9D F2UZ3bhKAHn7enb6E4RecOPi78GRw/S7wvRweSUs= From: "siddhesh at sourceware dot org" To: glibc-bugs@sourceware.org Subject: [Bug manual/28998] Document -D_FORTIFY_SOURCE Date: Thu, 08 Dec 2022 15:04:30 +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: siddhesh at sourceware dot org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: siddhesh at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to 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 Siddhesh Poyarekar changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at sourceware dot org |siddhesh at sourcew= are dot org --- Comment #7 from Siddhesh Poyarekar --- (In reply to Martin Liska from comment #6) > > Does it act like a failed > > assert() and call abort()? Is there a way to catch the exception like o= ne > > would catch SIGSEGV using a signal handler? >=20 > Likely not, Siddhesh, please correct me if I'm wrong. You could trap SIGABRT if you really really want to, but that's not a recommendation. > > Thanks. >=20 > Anyway, the documentation should be really improved and taken to GCC > compiler as well. I'm going to try writing something up for the glibc manual and gcc documentation. --=20 You are receiving this mail because: You are on the CC list for the bug.=