You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
(58) |
Apr
(261) |
May
(169) |
Jun
(214) |
Jul
(201) |
Aug
(219) |
Sep
(198) |
Oct
(203) |
Nov
(241) |
Dec
(94) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(137) |
Feb
(149) |
Mar
(150) |
Apr
(193) |
May
(95) |
Jun
(173) |
Jul
(137) |
Aug
(236) |
Sep
(157) |
Oct
(150) |
Nov
(136) |
Dec
(90) |
| 2005 |
Jan
(139) |
Feb
(130) |
Mar
(274) |
Apr
(138) |
May
(184) |
Jun
(152) |
Jul
(261) |
Aug
(409) |
Sep
(239) |
Oct
(241) |
Nov
(260) |
Dec
(137) |
| 2006 |
Jan
(191) |
Feb
(142) |
Mar
(169) |
Apr
(75) |
May
(141) |
Jun
(169) |
Jul
(131) |
Aug
(141) |
Sep
(192) |
Oct
(176) |
Nov
(142) |
Dec
(95) |
| 2007 |
Jan
(98) |
Feb
(120) |
Mar
(93) |
Apr
(96) |
May
(95) |
Jun
(65) |
Jul
(62) |
Aug
(56) |
Sep
(53) |
Oct
(95) |
Nov
(106) |
Dec
(87) |
| 2008 |
Jan
(58) |
Feb
(149) |
Mar
(175) |
Apr
(110) |
May
(106) |
Jun
(72) |
Jul
(55) |
Aug
(89) |
Sep
(26) |
Oct
(96) |
Nov
(83) |
Dec
(93) |
| 2009 |
Jan
(97) |
Feb
(106) |
Mar
(74) |
Apr
(64) |
May
(115) |
Jun
(83) |
Jul
(137) |
Aug
(103) |
Sep
(56) |
Oct
(59) |
Nov
(61) |
Dec
(37) |
| 2010 |
Jan
(94) |
Feb
(71) |
Mar
(53) |
Apr
(105) |
May
(79) |
Jun
(111) |
Jul
(110) |
Aug
(81) |
Sep
(50) |
Oct
(82) |
Nov
(49) |
Dec
(21) |
| 2011 |
Jan
(87) |
Feb
(105) |
Mar
(108) |
Apr
(99) |
May
(91) |
Jun
(94) |
Jul
(114) |
Aug
(77) |
Sep
(58) |
Oct
(58) |
Nov
(131) |
Dec
(62) |
| 2012 |
Jan
(76) |
Feb
(93) |
Mar
(68) |
Apr
(95) |
May
(62) |
Jun
(109) |
Jul
(90) |
Aug
(87) |
Sep
(49) |
Oct
(54) |
Nov
(66) |
Dec
(84) |
| 2013 |
Jan
(67) |
Feb
(52) |
Mar
(93) |
Apr
(65) |
May
(33) |
Jun
(34) |
Jul
(52) |
Aug
(42) |
Sep
(52) |
Oct
(48) |
Nov
(66) |
Dec
(14) |
| 2014 |
Jan
(66) |
Feb
(51) |
Mar
(34) |
Apr
(47) |
May
(58) |
Jun
(27) |
Jul
(52) |
Aug
(41) |
Sep
(78) |
Oct
(30) |
Nov
(28) |
Dec
(26) |
| 2015 |
Jan
(41) |
Feb
(42) |
Mar
(20) |
Apr
(73) |
May
(31) |
Jun
(48) |
Jul
(23) |
Aug
(55) |
Sep
(36) |
Oct
(47) |
Nov
(48) |
Dec
(41) |
| 2016 |
Jan
(32) |
Feb
(34) |
Mar
(33) |
Apr
(22) |
May
(14) |
Jun
(31) |
Jul
(29) |
Aug
(41) |
Sep
(17) |
Oct
(27) |
Nov
(38) |
Dec
(28) |
| 2017 |
Jan
(28) |
Feb
(30) |
Mar
(16) |
Apr
(9) |
May
(27) |
Jun
(57) |
Jul
(28) |
Aug
(43) |
Sep
(31) |
Oct
(20) |
Nov
(24) |
Dec
(18) |
| 2018 |
Jan
(34) |
Feb
(50) |
Mar
(18) |
Apr
(26) |
May
(13) |
Jun
(31) |
Jul
(13) |
Aug
(11) |
Sep
(15) |
Oct
(12) |
Nov
(18) |
Dec
(13) |
| 2019 |
Jan
(12) |
Feb
(29) |
Mar
(51) |
Apr
(22) |
May
(13) |
Jun
(20) |
Jul
(13) |
Aug
(12) |
Sep
(21) |
Oct
(6) |
Nov
(9) |
Dec
(5) |
| 2020 |
Jan
(13) |
Feb
(5) |
Mar
(25) |
Apr
(4) |
May
(40) |
Jun
(27) |
Jul
(5) |
Aug
(17) |
Sep
(21) |
Oct
(1) |
Nov
(5) |
Dec
(15) |
| 2021 |
Jan
(28) |
Feb
(6) |
Mar
(11) |
Apr
(5) |
May
(7) |
Jun
(8) |
Jul
(5) |
Aug
(5) |
Sep
(11) |
Oct
(9) |
Nov
(10) |
Dec
(12) |
| 2022 |
Jan
(7) |
Feb
(13) |
Mar
(8) |
Apr
(7) |
May
(12) |
Jun
(27) |
Jul
(14) |
Aug
(27) |
Sep
(27) |
Oct
(17) |
Nov
(17) |
Dec
|
| 2023 |
Jan
(10) |
Feb
(18) |
Mar
(9) |
Apr
(26) |
May
|
Jun
(13) |
Jul
(18) |
Aug
(5) |
Sep
(6) |
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
|
|
|
|
|
1
(5) |
|
2
(2) |
3
(15) |
4
(3) |
5
|
6
(11) |
7
(4) |
8
|
|
9
(3) |
10
(6) |
11
(4) |
12
(5) |
13
(7) |
14
(37) |
15
(8) |
|
16
(1) |
17
(19) |
18
(20) |
19
(20) |
20
(15) |
21
(13) |
22
|
|
23
|
24
(20) |
25
(6) |
26
(2) |
27
(4) |
28
(6) |
29
|
|
30
(5) |
|
|
|
|
|
|
|
From: <ar...@de...> - 2003-11-14 15:02:51
|
Hi all. I noticed that there is a report on valgrind 1.0.4 which mentions a segfault on machines without RDTSC. I'd like to know if this problem is still present in the current stable valgrind version. Thanks in advance. -- Andres Roldan Fluidsignal Group <ar...@fl...> The Debian Project <ar...@de...> GIGAX <ar...@gi...> GPG Key-ID 0xB29396EB Home Page http://people.fluidsignal.com/~aroldan |
|
From: Amol K. <am...@in...> - 2003-11-14 14:37:38
|
Hi Dimitri Thanks for the quick answer. I am getting the error in all the directories. I am using Red Hat Linux release 7.1 (Seawolf) Kernel 2.4.2-2. Yes I forgot to mention the "=" sign ..i.e. I tried ./configure --prefix=/usr/local/bin option as well. Any clues? Amolak -----Original Message----- From: Dimitri Papadopoulos-Orfanos [mailto:pap...@sh...] Sent: Friday, November 14, 2003 1:01 PM To: am...@in... Cc: val...@li... Subject: Re: [Valgrind-users] running valgrind on Red Hat Linux release 7.1 (Seawolf) Kernel 2.4.2-2 Hi, > I downloaded the valgrind sources (both Valgrind version 20031012 and > valgrind-2.0) from http://valgrind.kde.org. > > As per the README, used the following commands > > ./configure --prefix /usr/local/bin I think you mean: ./configure --prefix=/usr/local > make > make install > > I guess both the times the valgrind was compiled and installed > correctly. I also tried once with ./configure only (i.e. without giving > prefix option). Also tried using the setting up specific paths. But > still all the time I am getting the segmentation fault whenever I run > "./valgrind ls -al". This works for me: valgrind ls -al In which directory does this happen? > Can anybody tell me what could be the problem? Any information/steps > about this issues is welcome! Could you describe the system the segfault happens on? -- Dimitri |
|
From: Tom H. <th...@cy...> - 2003-11-14 14:36:33
|
In message <200...@gm...>
Dirk Mueller <dm...@gm...> wrote:
> On Friday 14 November 2003 14:41, Dimitri Papadopoulos-Orfanos wrote:
>
>> I'm trying to run valgrind-2.0.0 on a program that makes use of OpenGL
>> on Red Hat Linux 9. This is a dual-processor Dell with NVidia card and
>> latest drivers 1.0-4496. Valgrind dies. Any clue?
>
> you apparently compiled valgrind on a different system than you're
> running it on.
>
> try export LD_ASSUME_KERNEL=2.4.1
Actually I don't think it is that. Somebody else saw this with the
NVidia OpenGL drivers a while ago - it seems that they only supply
an NPTL version and don't mark the library in the right way for the
fallback to work when LD_ASSUME_KERNEL is set anyway.
Tom
--
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/
|
|
From: Randall H. <lis...@ch...> - 2003-11-14 14:35:17
|
Jeremy Fitzhardinge: |On Tue, 2003-11-11 at 14:43, Randall Hopper wrote: |> Switching to KDE, --assume-2.4=yes gets me past that error, but then after |> some minutes valgrinding this app locks my machine hard; it's completely |> net dead and console dead. Don't see this with my 9/23 CVS snapshot. |> |> BTW, this is on SuSE 8.2. | |Ah, well, that's what we like to call a kernel bug. No matter what junk |Valgrind does, it shouldn't lock the kernel like that. | |Obviously it could be a Valgrind bug too, and we'd like to fix it, but I |wonder if there's a kernel update from SuSE, or perhaps you could try |just installing a stock 2.4 kernel? SuSE does have a kernel update, which I'm running. I can try a stock kernel later. |What does your app do? Does it have lots of threads? Do lots of |syscalls? Does it seem to be all working fine, and then it all falls |over, or does it gradually collapse? Any oopses or other kernel |messages on the console? The app has about 10 threads, one using OpenGL. Probably a fair. It seems to be working fine, albeit slowly compared to previous valgrind snaps and eventually the GUI just freezes and it quits responding to events. Same with keyboard, net, etc. xosview doesn't suggest that we're running out of memory -- I have a Gig on this box (though this valgrind snap was consuming more than previous snaps) . No other clues that I'm aware of. The ATI OpenGL drivers do use SSE which valgrind doesn't quite deal with right yet, but I was only debugging app startup which used to work fine with older snaps. Sorry I can't provide more useful input. I'm not really sure what to look for. Randall |
|
From: Dimitri Papadopoulos-O. <pap...@sh...> - 2003-11-14 14:19:58
|
Hi, I get these warnings on a Red Hat 9 machine: $ valgrind ls [...] ==14433== Memcheck, a.k.a. Valgrind, a memory error detector for x86-linux. ==14433== Copyright (C) 2002-2003, and GNU GPL'd, by Julian Seward. ==14433== Using valgrind-2.0.0, a program supervision framework for x86-linux. ==14433== Copyright (C) 2000-2003, and GNU GPL'd, by Julian Seward. ==14433== Estimated CPU clock rate is 1995 MHz ==14433== For more details, rerun with: -v ==14433== ==14433== Warning: attempt to set SIGKILL handler in __NR_sigaction. ==14433== Warning: attempt to set SIGSTOP handler in __NR_sigaction. [...] What do they mean exactly? Should these warnings be ignored? Should the program be fixed? -- Dimitri |
|
From: Dimitri Papadopoulos-O. <pap...@sh...> - 2003-11-14 14:17:02
|
Hi, >>I'm trying to run valgrind-2.0.0 on a program that makes use of OpenGL >>on Red Hat Linux 9. This is a dual-processor Dell with NVidia card and >>latest drivers 1.0-4496. Valgrind dies. Any clue? > > > you apparently compiled valgrind on a different system than you're running it > on. No, it was compiled on the same machine. > try export LD_ASSUME_KERNEL=2.4.1 Isn't Valgrind 2.0.0 supposed to set this variable itself? Anyway, it doesn't help. The error message remains the same. -- Dimitri |
|
From: Dirk M. <dm...@gm...> - 2003-11-14 14:06:18
|
On Friday 14 November 2003 14:41, Dimitri Papadopoulos-Orfanos wrote: > I'm trying to run valgrind-2.0.0 on a program that makes use of OpenGL > on Red Hat Linux 9. This is a dual-processor Dell with NVidia card and > latest drivers 1.0-4496. Valgrind dies. Any clue? you apparently compiled valgrind on a different system than you're running it on. try export LD_ASSUME_KERNEL=2.4.1 |
|
From: Dimitri Papadopoulos-O. <pap...@sh...> - 2003-11-14 13:57:56
|
Hi, In case of internal problems, valgrind prints the following message : ==14346== Memcheck, a.k.a. Valgrind, a memory error detector for x86-linux. ==14346== Copyright (C) 2002-2003, and GNU GPL'd, by Julian Seward. ==14346== Using valgrind-2.0.0, a program supervision framework for x86-linux. ==14346== Copyright (C) 2000-2003, and GNU GPL'd, by Julian Seward. [...] Note: see also the FAQ.txt in the source distribution. It contains workarounds to several common problems. If that doesn't help, please report this bug to: js...@ac... In the bug report, send all the above text, the valgrind version, and what Linux distro you are using. Thanks. Two remarks: * According to the Web site: http://valgrind.kde.org/bugs.html bug reports should be sent to this mailing list, not directly to jseward@. * The valgrind version is already present in "the above text", so the message should probably be changed to: In the bug report, send all the above text, and what Linux distro you are using. Thanks. -- Dimitri |
|
From: Dimitri Papadopoulos-O. <pap...@sh...> - 2003-11-14 13:39:22
|
Hi, I'm trying to run valgrind-2.0.0 on a program that makes use of OpenGL on Red Hat Linux 9. This is a dual-processor Dell with NVidia card and latest drivers 1.0-4496. Valgrind dies. Any clue? $ setenv __GL_FORCE_GENERIC_CPU 1 $ valgrind anatomist.bin ==14331== Memcheck, a.k.a. Valgrind, a memory error detector for x86-linux. ==14331== Copyright (C) 2002-2003, and GNU GPL'd, by Julian Seward. ==14331== Using valgrind-2.0.0, a program supervision framework for x86-linux. ==14331== Copyright (C) 2000-2003, and GNU GPL'd, by Julian Seward. ==14331== Estimated CPU clock rate is 1996 MHz ==14331== For more details, rerun with: -v ==14331== valgrind: vg_ldt.c:167 (vgPlain_do_useseg): Assertion `(seg_selector & 7) == 7' failed. sched status: Thread 1: status = Runnable, associated_mx = 0x0, associated_cv = 0x0 ==14331== at 0x41643641: __nvsym18200 (in /usr/lib/tls/libGL.so.1.0.4496) Note: see also the FAQ.txt in the source distribution. It contains workarounds to several common problems. If that doesn't help, please report this bug to: js...@ac... In the bug report, send all the above text, the valgrind version, and what Linux distro you are using. Thanks. $ -- Dimitri |
|
From: Dimitri Papadopoulos-O. <pap...@sh...> - 2003-11-14 12:58:49
|
Hi, > I downloaded the valgrind sources (both Valgrind version 20031012 and > valgrind-2.0) from http://valgrind.kde.org. > > As per the README, used the following commands > > ./configure --prefix /usr/local/bin I think you mean: ./configure --prefix=/usr/local > make > make install > > I guess both the times the valgrind was compiled and installed > correctly. I also tried once with ./configure only (i.e. without giving > prefix option). Also tried using the setting up specific paths. But > still all the time I am getting the segmentation fault whenever I run > "./valgrind ls -al". This works for me: valgrind ls -al In which directory does this happen? > Can anybody tell me what could be the problem? Any information/steps > about this issues is welcome! Could you describe the system the segfault happens on? -- Dimitri |
|
From: Melchior F. <mf...@kd...> - 2003-11-14 12:43:41
|
* Melchior FRANZ -- Friday 14 November 2003 00:14: > * Nicholas Nethercote -- Thursday 13 November 2003 23:55: > > I'm sorry, I don't understand. These errors you want to attach GDB to -- > > are they being suppressed? It would help if you could explain what you're > > doing in more detail. > > No. They are shown, [...] No wait. They are shown if the rule doesn't match (because I made a change to any of the fun: lines, such as removing or adding a letter). Otherwise, if the rule matches, vg only displays ==20796== ---- Attach to GDB ? --- [Return/N/n/Y/y/C/c] ---- after the next (unsuppressed) error, but doesn't really let me type 'y' but instantly displays the next error, after which it doesn't stop either, and so on. All error messages rush by. As I told you, I know the reason for all that (-> the unhandled -EAGAIN), but I don't know how this particular suppression rule could have any impact on this seemingly unrelated issue. m. |
|
From: Test V. <am...@in...> - 2003-11-14 11:39:30
|
Hi All, I downloaded the valgrind sources (both Valgrind version 20031012 and valgrind-2.0) from http://valgrind.kde.org. As per the README, used the following commands ./configure --prefix /usr/local/bin make make install I guess both the times the valgrind was compiled and installed correctly. I also tried once with ./configure only (i.e. without giving prefix option). Also tried using the setting up specific paths. But still all the time I am getting the segmentation fault whenever I run "./valgrind ls -al". Can anybody tell me what could be the problem? Any information/steps about this issues is welcome! Best regards AMOLAK |