From: Frederic Weisbecker <fweisbec@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org
Subject: Re: [BUG] fault while using perf callchains in sparc64
Date: Thu, 1 Apr 2010 11:38:33 +0200 [thread overview]
Message-ID: <20100401093831.GE5207@nowhere> (raw)
In-Reply-To: <20100401.010903.05627158.davem@davemloft.net>
On Thu, Apr 01, 2010 at 01:09:03AM -0700, David Miller wrote:
> From: Frederic Weisbecker <fweisbec@gmail.com>
> Date: Thu, 1 Apr 2010 11:06:11 +0200
>
> > I actually can't. It works well on a backup 2.6.31-rc6 kernel
> > but when I build a new one of this same version, the problem
> > happens again. And I don't have the config of the one that works
> > (and no /proc/config.gz as well).
> >
> > So I suspect this is something that happens with some specific
> > configs only.
> >
> > Anyway, once I get more clues about this, I'll tell you.
>
> I was going to ask you if any of your compiler tools changed
> recently...
>
> Check the gcc version printed by the working kernel at the top of the
> dmesg logs and compare to what you end up using now.
They are exactly the same :)
gcc version 4.3.2 (Debian 4.3.2-1.1)
Really I think I need to dig further as I don't have useful
clues to provide. I need to check if the segfault always happen
in the same place, etc...
It seems to happen with ld as well btw (not sure this is related
though):
[ 3366.005962] ld[19041]: segfault at 10 ip 000000007010248c (rpc 00000000701023f8) sp 00000000ffda87c8 error 30001
in libbfd-2.18.0.20080103.so[700d8000+a0000]
next prev parent reply other threads:[~2010-04-01 8:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-28 4:34 [BUG] fault while using perf callchains in sparc64 Frederic Weisbecker
2010-03-29 2:02 ` David Miller
2010-03-29 3:23 ` Frederic Weisbecker
2010-03-29 19:56 ` David Miller
2010-03-29 20:09 ` David Miller
2010-03-29 20:49 ` Frederic Weisbecker
2010-03-29 21:01 ` David Miller
2010-03-29 21:11 ` Frederic Weisbecker
2010-03-29 21:19 ` David Miller
2010-03-29 21:28 ` Frederic Weisbecker
2010-03-29 22:02 ` David Miller
2010-03-29 22:21 ` Frederic Weisbecker
2010-03-29 22:32 ` David Miller
2010-04-01 9:06 ` Frederic Weisbecker
2010-04-01 8:09 ` David Miller
2010-04-01 9:38 ` Frederic Weisbecker [this message]
2010-04-01 9:02 ` David Miller
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=20100401093831.GE5207@nowhere \
--to=fweisbec@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@vger.kernel.org \
/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