Bug#426204: Segmentation fault: *** glibc detected *** powertop: munmap_chunk(): invalid

2007-05-30 Thread Josh Triplett
Petter Reinholdtsen wrote:
 If you can reproduce the problem, try running powetop in valgrind to
 pinpoint it.  You can run it like this to not mess up the output:
 
   valgrind --log-file=/tmp/powertoplog powertop
 
 valgrind work best if powertop is compiled with debug information
 included (-g) and not stripped, but it might give some clues about the
 problem even without debug information in the binary.

I haven't managed to reproduce the problem yet.

When I did reproduce it, it happened when I left it running for a while, and
ran various wakeup-heavy programs (such as OpenGL programs that never slept).
I've tried similar workloads, and haven't reproduced the problem.

- Josh Triplett




signature.asc
Description: OpenPGP digital signature


Bug#426204: Segmentation fault: *** glibc detected *** powertop: munmap_chunk(): invalid

2007-05-28 Thread Petter Reinholdtsen

If you can reproduce the problem, try running powetop in valgrind to
pinpoint it.  You can run it like this to not mess up the output:

  valgrind --log-file=/tmp/powertoplog powertop

valgrind work best if powertop is compiled with debug information
included (-g) and not stripped, but it might give some clues about the
problem even without debug information in the binary.

Happy hacking,
-- 
Petter Reinholdtsen


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#426204: Segmentation fault: *** glibc detected *** powertop: munmap_chunk(): invalid

2007-05-28 Thread Patrick Winnertz
I tried yesterday 10 hours to reproduce the problem on my laptop (intel
centrino duo) but after this time powertop still runs without any problems. 

Arjan (Upstream) tries to reproduce it, but he can't reproduce it, too. 

Greetings
Patrick

Petter Reinholdtsen schrieb am Monday, den 28. May 2007:

 
 If you can reproduce the problem, try running powetop in valgrind to
 pinpoint it.  You can run it like this to not mess up the output:
 
   valgrind --log-file=/tmp/powertoplog powertop
 
 valgrind work best if powertop is compiled with debug information
 included (-g) and not stripped, but it might give some clues about the
 problem even without debug information in the binary.
 
 Happy hacking,
 -- 
 Petter Reinholdtsen
 

-- 
 .''`.   Patrick Winnertz [EMAIL PROTECTED]
: :'  :  GNU/Linux Debian-Edu Developer
`. `'`   http://www.der-winnie.de http://d.skolelinux.org/~winnie
  `-  Debian - when you have better things to do than fixing systems
 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#426204: Segmentation fault: *** glibc detected *** powertop: munmap_chunk(): invalid pointer: 0x080f1170

2007-05-27 Thread Josh Triplett
Package: powertop
Version: 1.4-1
Severity: important

I left powertop running for a while, and got this:

*** glibc detected *** powertop: munmap_chunk(): invalid pointer: 0x080f1170 ***

- Josh Triplett

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.22-rc1 (PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages powertop depends on:
ii  libc6 2.5-9  GNU C Library: Shared libraries
ii  libncurses5   5.6-3  Shared libraries for terminal hand

powertop recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]