This is the mail archive of the
mailing list for the glibc project.
[Bug libc/12189] __stack_chk_fail should not attempt a backtrace
- From: "carlos at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Tue, 03 Sep 2013 20:43:03 +0000
- Subject: [Bug libc/12189] __stack_chk_fail should not attempt a backtrace
- Auto-submitted: auto-generated
- References: <bug-12189-131 at http dot sourceware dot org/bugzilla/>
--- Comment #11 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to firstname.lastname@example.org from comment #9)
> On Fri, 30 Aug 2013, carlos at redhat dot com wrote:
> > We have ABRT_INSTRUCTION in glibc for all targets and we could use it in this
> I see no sign of ABORT_INSTRUCTION for aarch64, alpha, am33 or arm.
It is a QoI issue, it wouldn't be hard to add something for all of these
I would like to make it mandatory that all machines implement
ABORT_INSTRUCTION, but haven't suggested it yet.
It's the only way in which glibc aborts in situations where a function call
can't be made or error conditions have forced us into a fallback e.g.
check_one_fd, abort, _exit.
You are receiving this mail because:
You are on the CC list for the bug.