From: Sergey Senozhatsky <sergey.senozhatsky at gmail.com>
To: powertop@lists.01.org
Subject: Re: [Powertop] [bugreport] crash on powertop --debug --html=file.html
Date: Wed, 27 Jun 2012 19:32:42 +0300 [thread overview]
Message-ID: <20120627163242.GD2996@swordfish.datadirect.datadirectnet.com> (raw)
In-Reply-To: 201206271142.20502.dl9pf@gmx.de
[-- Attachment #1: Type: text/plain, Size: 834 bytes --]
On (06/27/12 11:42), Jan-Simon Möller wrote:
> > > (i=0x875720, j=0x211)
> >
> > Hm, it seems pretty unlikely that std::allocator would allocate anything
> > on such a low address. It rather expected i and j to be somewhere in
> > -/+ N * sizeof(struct)
> > range.
> >
> > So, there is something we don't known about your system, or we have
> > memory corruption which I can't find at the moment.
>
> Nothing special, just opensuse 11.4 with all updates.
> It works fine on the same setup with an i586 kernel/userspace.
>
> I'll look into that a bit more.
>
Could you please run
valgrind --tool=memcheck --leak-check=full --show-reachable=yes --leak-resolution=high --track-origins=yes -v --log-file=./powertop-memcheck powertop --debug --html=file.html
and provide powertop-memcheck file?
-ss
next reply other threads:[~2012-06-27 16:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 16:32 Sergey Senozhatsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-07-06 9:00 [Powertop] [bugreport] crash on powertop --debug --html=file.html Sergey Senozhatsky
2012-07-01 20:07
2012-07-01 18:13 Sergey Senozhatsky
2012-07-01 13:46
2012-06-27 16:37 Sergey Senozhatsky
2012-06-27 13:57 Arjan van de Ven
2012-06-27 9:42
2012-06-27 8:06 Sergey Senozhatsky
2012-06-26 19:09
2012-06-26 18:50 Chris Ferron
2012-06-26 18:42 Chris Ferron
2012-06-26 15:10
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=20120627163242.GD2996@swordfish.datadirect.datadirectnet.com \
--to=powertop@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.