From: Alexandra Yates <alexandra.yates at linux.intel.com>
To: powertop@lists.01.org
Subject: Re: [Powertop] close_display() sigsegv
Date: Thu, 20 Nov 2014 17:06:32 -0800 [thread overview]
Message-ID: <51714.10.24.1.226.1416531992.squirrel@linux.intel.com> (raw)
In-Reply-To: CAG27Bk0_Aur0GxHEC=T6zD+o9zLHigiNvwajUB-yJtXOupRcaA@mail.gmail.com
[-- Attachment #1: Type: text/plain, Size: 2298 bytes --]
> On 20 November 2014 19:47, Alexandra Yates
> <alexandra.yates(a)linux.intel.com> wrote:
>
> Hi Alexandra,
>
>> Followed all steps, in two platforms still cant reproduce. (Difference)
>> I'm running Ubuntu.
>
> I just reproduced the issue with g++, without CFLAGS, or anything in
> environment that I could tell would effect to compilation. Backtrace
> is pretty similar.
>
> (gdb) bt full
> #0 0x000000000040a14e in _M_lower_bound (this=<optimized out>,
> __k=<error reading variable: Cannot access memory at address
> 0xffffffffffffffe8>, __y=0x477368 <tab_windows+8>, __x=0x363e930)
> at /usr/include/c++/4.9.2/bits/stl_tree.h:1260
> No locals.
> #1 lower_bound (__k=<error reading variable: Cannot access memory at
> address 0xffffffffffffffe8>, this=0x477360 <tab_windows>) at
> /usr/include/c++/4.9.2/bits/stl_tree.h:927
> No locals.
> #2 lower_bound (__x=<error reading variable: Cannot access memory at
> address 0xffffffffffffffe8>, this=0x477360 <tab_windows>) at
> /usr/include/c++/4.9.2/bits/stl_map.h:902
> No locals.
> #3 operator[] (__k=<error reading variable: Cannot access memory at
> address 0xffffffffffffffe8>, this=0x477360 <tab_windows>) at
> /usr/include/c++/4.9.2/bits/stl_map.h:496
> __i = <optimized out>
> #4 close_display () at display.cpp:93
> i = 5
> #5 0x0000000000411e5e in clean_shutdown () at main.cpp:378
> No locals.
> #6 0x0000000000406d6d in main (argc=1, argv=0x7fff51015798) at
> main.cpp:519
> option_index = 0
> c = <optimized out>
> iterations = 1
> filename = '\000' <repeats 2928 times>...
> workload = '\000' <repeats 4095 times>
> auto_tune = 0
>
> Maybe comparing my config.log with your will give a hint what could be
> going on.
>
> http://ut3.org/~kerolasa/config.log.gz
>
>> I will revert the culprit commit. I would appreciate you testing again.
>
> I think the line below should be removed as well.
>
Where you able to test that you issue is resolved without these lines?
> main.cpp: In function 'void clean_shutdown()':
> main.cpp:378:16: error: 'close_display' was not declared in this scope
> close_display();
>
> --
> Sami Kerola
> http://www.iki.fi/kerolasa/
>
Thank you,
Alexandra.
next reply other threads:[~2014-11-21 1:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 1:06 Alexandra Yates [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-11-21 6:26 [Powertop] close_display() sigsegv Sami Kerola
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-19 1:43 Joe Konno
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=51714.10.24.1.226.1416531992.squirrel@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.