From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Marc Khouzam <marc.khouzam@ericsson.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [patch] ON_STACK: Warn on buggy Linux i386 kernels
Date: Sat, 21 Jul 2012 07:53:00 -0000 [thread overview]
Message-ID: <20120721075233.GA1268@host2.jankratochvil.net> (raw)
In-Reply-To: <F7CE05678329534C957159168FA70DEC597936B72F@EUSAACMS0703.eamcs.ericsson.se>
On Sat, 21 Jul 2012 04:58:39 +0200, Marc Khouzam wrote:
> > From: Jan Kratochvil [jan.kratochvil@redhat.com]
> > But I have found ubuntu-12.04-dvd-i386.iso (both GA and latest updates) which
> > is LTS (=still maintained) is also affected by this problem so I expect there
> > maybe vocal feedback.
>
> That's me :) I'm seeing this warning. IIUC I can safely ignore this warning?
Be prepared if you do some:
(gdb) print somefunction(1, 2, 3)
when it will segfault.
The goal is to convince your OS vendor they should fix it.
(Or to switch OS from 12 years dead i686 arch to x86_64.)
Regards,
Jan
prev parent reply other threads:[~2012-07-21 7:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 14:27 Jan Kratochvil
2012-07-03 15:02 ` [patchv2] " Jan Kratochvil
2012-07-07 12:14 ` [commit] " Jan Kratochvil
2012-07-21 2:58 ` [patch] " Marc Khouzam
2012-07-21 7:53 ` Jan Kratochvil [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120721075233.GA1268@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=marc.khouzam@ericsson.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox