From: Joe Konno <joe.konno at linux.intel.com>
To: powertop@lists.01.org
Subject: Re: [Powertop] close_display() sigsegv
Date: Tue, 18 Nov 2014 17:43:10 -0800 [thread overview]
Message-ID: <546BF5AE.3020705@linux.intel.com> (raw)
In-Reply-To: CAG27Bk39ET-Ccz0ahfufUwHgxQiWKj=MCioVx+3ztomLtwXxng@mail.gmail.com
[-- Attachment #1: Type: text/plain, Size: 940 bytes --]
The game of whack-a-mole continues. Good find, Sami.
Alex, suggest we revert the errant patch. Memory management as a whole
within the tool deserves (much) more time and focus than a few
band-aids, so I wouldn't be opposed to reverting the entire series (of 5).
On 11/18/2014 02:29 PM, Sami Kerola wrote:
> Hello,
>
> It might be good idea to check before final release if the issue
> reported in this email can be reproduced.
>
> $ echo $CC
> clang
> $ echo $CFLAGS
> -O0 -g -ggdb -Wall -Wextra -pedantic -fno-omit-frame-pointer
> $ echo $LD
> ld.gold
>
> After compiling the version above I always get crash.
>
> $ git describe
> v2.7-rc1-1-g959227c
>
> $ ./src/powertop
> ....
> Leaving PowerTOPtimates do 21 measurement(s) connected to battery only
> Segmentation fault (core dumped)
>
> It looks like commit 706bc28ff536f4f53fdf6e24178b9e3bac67d53f might
> have something to do with the issue.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2014-11-19 1:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-19 1:43 Joe Konno [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-11-21 6:26 [Powertop] close_display() sigsegv Sami Kerola
2014-11-21 1:06 Alexandra Yates
2014-11-20 21:51 Sami Kerola
2014-11-20 19:47 Alexandra Yates
2014-11-20 15:02 Sami Kerola
2014-11-20 4:13 Alexandra Yates
2014-11-18 22:29 Sami Kerola
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=546BF5AE.3020705@linux.intel.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.