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
(1) |
2
(8) |
3
(26) |
4
(14) |
5
(23) |
6
(8) |
7
(6) |
|
8
(1) |
9
(5) |
10
|
11
(7) |
12
|
13
(4) |
14
(2) |
|
15
|
16
(6) |
17
(4) |
18
(18) |
19
(10) |
20
(13) |
21
(2) |
|
22
|
23
(1) |
24
(7) |
25
(13) |
26
(35) |
27
(5) |
28
(2) |
|
29
(3) |
30
(5) |
31
(7) |
|
|
|
|
|
From: Nicholas N. <nj...@ca...> - 2004-08-24 08:42:11
|
On Mon, 23 Aug 2004, George Huber wrote: > I remember seeing some discussion of a windows port of > valgrind awhile back. I was wondering what the status > of the port was - assuming some one was still working > on it. AIUI it's preliminary discussions only, and is a long way from actually happening. N |
|
From: George H. <kh...@op...> - 2004-08-24 03:59:09
|
All, I remember seeing some discussion of a windows port of valgrind awhile back. I was wondering what the status of the port was - assuming some one was still working on it. Thanks, George |
|
From: Nicholas N. <nj...@ca...> - 2004-08-23 10:31:39
|
On Wed, 18 Aug 2004, I K wrote: > Operating system name and version : Red Hat Linux 2.4.18-3bigmem > Valgrind version: valgrind-2.1.2 > > I am not sure about the split. But I can find out. > > The output of "cat /proc/self/maps" : > > 08048000-0804c000 r-xp 00000000 03:06 328393 /bin/cat > 0804c000-0804d000 rw-p 00003000 03:06 328393 /bin/cat > [...] > bfffb000-c0000000 rwxp ffffc000 00:00 0 Hmm, that looks like a pretty normal 3G:1G layout that should not cause any problems. > "--tool=none" works fine. Even "--tool=addrcheck" is working now most of the > times ! However, " --tool=memcheck" is not working at all and always gives : > > valgrind: vg_main.c:553 (layout_remaining_space): Assertion `(void*)-1 != > vres" failed. > > My guess is that "--tool=memcheck" requires huge memory that the system is > unable to provide. Is this right? Memcheck requires a lot of address space, but not necessarily a lot of memory; it depends how big the client program is. Physical memory size certainly should not be an issue for small programs, and you say even they aren't working with Memcheck. I'm afraid I'm nonplussed by this, and don't know what else to suggest. N |
|
From: Tom H. <th...@cy...> - 2004-08-21 06:39:02
|
In message <412...@ci...>
Tom Hu <to...@ci...> wrote:
> Syscall param socketcall.sendto(msg) contains uninitialised or
> unaddressable byte(s)
> However, there are 5 parameters passed to this systcall. Is any better
Actually there are six arguments, and it is telling you which one
by putting (msg) after the name. That means it is the actual message
being sent - ie the buffer argument.
Tom
--
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/
|
|
From: Tom Hu <to...@ci...> - 2004-08-21 00:57:51
|
I got this error: Syscall param socketcall.sendto(msg) contains uninitialised or unaddressable byte(s) However, there are 5 parameters passed to this systcall. Is any better way to find which parameter causes this error? Thanks, Tom Hu |
|
From: Tom H. <th...@cy...> - 2004-08-20 12:50:35
|
In message <412...@ya...>
pan...@ya... wrote:
> 1. But can we not trap signal(), sigaction() calls (similar to
> trapping malloc etc) to register the user function ptr
> in a internal data structure and then on the actual signal
> we do our job and then call user function ?
We already virtualise the signal handling anyway. The problem with
your suggestion is that the signal winds up having two effects, one
on valgrind and one on the target program, and that's pretty nasty.
Tom
--
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/
|
|
From: pkr <pan...@ya...> - 2004-08-20 12:12:31
|
Not sure whether this is possible in valgrind.... 1. But can we not trap signal(), sigaction() calls (similar to trapping malloc etc) to register the user function ptr in a internal data structure and then on the actual signal we do our job and then call user function ? 2. And then the signal number can always be cmdline parameter so that user is free to select a appropriate signal (some of them are unused ie SIGUSR1 etc) and then user is also warned that this signal wont be passed to the program.. Thanks, Pankaj Tom Hughes wrote: > In message <412...@ya...> > pkr <pan...@ya...> wrote: > > >>My intention was about leak report only. It would be good to have >>some way of notifying (signal) valgrind to generate the report. >>As there could be situations when the above api cant be inserted in >>the code... > > > The problem is that if valgrind starting acting on signals it > would break programs which used that signal themselves - there > is no separate valgrind process to send the signal to. > > Tom > |
|
From: Nicholas N. <nj...@ca...> - 2004-08-20 08:40:23
|
On Mon, 9 Aug 2004, Oswald Buddenhagen wrote: > btw, ever thought about valgrinding valgrind (which valgrinds another > valgrind :)? Sure, it's the first thing everyone tries :) > with a dynamic load address this shouldn't be a major problem any more. > ok, for me, even the most trivial "valgrind valgrind" just segfaults, > but i suppose this is easily fixable. I don't think it's that easy. Then again, I'd be happy to be proven wrong, patches are welcome :) I once had self-hosting briefly working in the LD_PRELOAD days, by statically linking V with a program, and then running that combination under another V. There were difficulties with the inner V doing clever things that fooled the outer V and gave spurious errors. I didn't do much with it, and then we switched to FV and that stopped working. N |
|
From: Nicholas N. <nj...@ca...> - 2004-08-20 08:19:35
|
On Fri, 20 Aug 2004, Tom Hughes wrote: >> Im new user of Valgrind, and I dont know how to read his >> output.. anybody can explain what is a "Invalid read of size X" .. and >> can describe where is my error here (im gettin lots of these erros.. >> lol): > > It means your program is making an invalid read of size X bytes. In > other words it is reading through a pointer whose value is not properly > initialised. Er, no; the pointer itself is fine. But your program is accessing memory it should not. The 2nd half of your error shows that you are accessing memory inside a heap block that has been freed. See the manual for more details. N |
|
From: Nicholas N. <nj...@ca...> - 2004-08-20 08:16:14
|
On Thu, 19 Aug 2004, Samofatov, Nickolay wrote: > --8435-- INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - > exiting > --8435-- si_code=1 Fault EIP: 0xB003905A; Faulting address: 0xBF7FFFFC > > I'm probably doing something wrong, but I'm stuck here at the moment. > Problem is reliably reproducable and test works fine when running not > under Valgrind. > Machine is vanilla Mandrake 10 installation, Valgrind 2.1.2 is built > from source using stock compiler. > Firebird is the checkout from CVS HEAD a few days old, I may prepare > testcase bundle if there is an interest. > Any suggestions? Urgh, Valgrind itself is seg faulting -- definitely a Valgrind bug. Trouble is, these are really hard to track down, almost impossible without a test program. It does seem strange that 0xBF7FFFFC is the faulting address, since that's on the stack. And it looks like the stack has just extended to a new page. I wonder if that's involved somehow... If you're feeling adventurous, you could try inserting VG_(printf)() calls (or OINK() calls) in vg_signals.c:vg_sync_signalhandler() and try to work out if something is going wrong in there. Particularly around line 2106, where the comment says "extend the stack segment". You could also make a bug report in Bugzilla. Thanks. N |
|
From: Dimitri Papadopoulos-O. <pap...@sh...> - 2004-08-20 08:05:18
|
Hi,
> This is very simple error. The error looks like it does not like my file
> format:
>
> x> valgrind --tool=memcheck --suppressions=/users/tomhu/log5.supp
> ./my_program
> ==4293== Memcheck, a memory error detector for x86-linux.
> ==4293== Copyright (C) 2002-2004, and GNU GPL'd, by Julian Seward.
> ==4293== Using valgrind-2.1.1, a program supervision framework for
> x86-linux.
> ==4293== Copyright (C) 2000-2004, and GNU GPL'd, by Julian Seward.
> ==4293== FATAL: in suppressions file: `/users/tomhu/log5.supp': syntax
> error on: {
> ==4293== exiting now.
I can't repdroduce that, at least not with Valgrind 2.1.2. Maybe there
are hidden characters in your suppresion file, such as DOS line feeds?
Dimitri
|
|
From: Nicholas N. <nj...@ca...> - 2004-08-20 08:04:15
|
On Thu, 19 Aug 2004, Robert Walsh wrote: > One way of doing this is to have Valgrind open a socket and check it for > requests generated by a companion client program every so often. Sounds > like it might slow things down, though. Should be simple to code up and > measure, though. Another recent discussion was based around using signals, but letting the user specify which signal on the command line. So you could, for example, using SIGINT for leak checking on Ctrl-C in interactive programs (maybe using a prompt which asks, when you get a SIGINT, whether to do a leak-check or just treat the signal normally). N |
|
From: Robert W. <rj...@du...> - 2004-08-20 06:26:12
|
> > My intention was about leak report only. It would be good to have > > some way of notifying (signal) valgrind to generate the report. > > As there could be situations when the above api cant be inserted in > > the code... >=20 > The problem is that if valgrind starting acting on signals it > would break programs which used that signal themselves - there > is no separate valgrind process to send the signal to. One way of doing this is to have Valgrind open a socket and check it for requests generated by a companion client program every so often. Sounds like it might slow things down, though. Should be simple to code up and measure, though. Regards, Robert. --=20 Robert Walsh Amalgamated Durables, Inc. - "We don't make the things you buy." Email: rj...@du... |
|
From: Tom H. <th...@cy...> - 2004-08-20 06:21:04
|
In message <200...@bi...>
Danny Angelo Carminati Grein <val...@bi...> wrote:
> Im new user of Valgrind, and I dont know how to read his
> output.. anybody can explain what is a "Invalid read of size X" .. and
> can describe where is my error here (im gettin lots of these erros..
> lol):
It means your program is making an invalid read of size X bytes. In
other words it is reading through a pointer whose value is not properly
initialised.
Tom
--
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/
|
|
From: Tom H. <th...@cy...> - 2004-08-20 06:19:25
|
In message <412...@ya...>
pkr <pan...@ya...> wrote:
> My intention was about leak report only. It would be good to have
> some way of notifying (signal) valgrind to generate the report.
> As there could be situations when the above api cant be inserted in
> the code...
The problem is that if valgrind starting acting on signals it
would break programs which used that signal themselves - there
is no separate valgrind process to send the signal to.
Tom
--
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/
|
|
From: pkr <pan...@ya...> - 2004-08-20 05:32:35
|
Tom Hughes wrote: > In message <412...@ya...> > pan...@ya... wrote: > > >>2. Is it possible for valgrind to generate its report on some other >>event apart from program exit ? ie I have a daemon which is up 24x7 and >>would like to collect the valgrind report at specific time intervals. > > > Memory access problems are reported as they happen. Memory leaks are > reported on exit or when the VALGRIND_DO_LEAK_CHECK client request is > used by the target program. > My intention was about leak report only. It would be good to have some way of notifying (signal) valgrind to generate the report. As there could be situations when the above api cant be inserted in the code... Thanks, Pankaj > Tom > |
|
From: Samofatov, N.
|
Hi, Dear Valgrind developers! I'm trying to perform some testing of Firebird database engine under Valgrind. This time I tried to verify single-process multi-threaded build. I ported Firebird to the subset of POSIX threads API supported by Valgrind 2.1.2, it was not difficult since Firebird is generally portable. I only had to disable some of Linux-specific optimizations. Multi-threaded firebird currently passes some basic testing, but if I try to switch doing something less trivial, for example, restore one of my test databases Valgrind crashes like that: ---------------------------------------------------- =3D=3D8435=3D=3D Memcheck, a memory error detector for x86-linux. =3D=3D8435=3D=3D Copyright (C) 2002-2004, and GNU GPL'd, by Julian = Seward et al. =3D=3D8435=3D=3D Using valgrind-2.1.2, a program supervision framework = for x86-linux. =3D=3D8435=3D=3D Copyright (C) 2000-2004, and GNU GPL'd, by Julian = Seward et al. =3D=3D8435=3D=3D For more details, rerun with: -v =3D=3D8435=3D=3D =3D=3D8435=3D=3D Warning: noted but unhandled ioctl 0x5422 with no size/direction hints =3D=3D8435=3D=3D This could cause spurious value errors to appear. =3D=3D8435=3D=3D See README_MISSING_SYSCALL_OR_IOCTL for guidance on = writing a proper wrapper. =3D=3D8435=3D=3D warning: Valgrind's pthread_cond_destroy is incomplete =3D=3D8435=3D=3D (it doesn't check if the cond is waited on) =3D=3D8435=3D=3D your program may misbehave as a result =3D=3D8435=3D=3D warning: Valgrind's pthread_cond_destroy is incomplete =3D=3D8435=3D=3D (it doesn't check if the cond is waited on) =3D=3D8435=3D=3D your program may misbehave as a result =3D=3D8435=3D=3D warning: Valgrind's pthread_cond_destroy is incomplete =3D=3D8435=3D=3D (it doesn't check if the cond is waited on) =3D=3D8435=3D=3D your program may misbehave as a result --8435-- INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - exiting --8435-- si_code=3D1 Fault EIP: 0xB003905A; Faulting address: 0xBF7FFFFC valgrind: the `impossible' happened: Killed by fatal signal Basic block ctr is approximately 654850000 =3D=3D8435=3D=3D at 0xB002BE0A: vgPlain_core_panic (vg_mylibc.c:1188) =3D=3D8435=3D=3D by 0xB002BE09: panic (vg_mylibc.c:1184) =3D=3D8435=3D=3D by 0xB002BE1E: vgPlain_core_panic (vg_mylibc.c:1189) =3D=3D8435=3D=3D by 0xB0032295: vg_sync_signalhandler = (vg_signals.c:2225) =3D=3D8435=3D=3D by 0xB0045499: (within = /usr/local/lib/valgrind/stage2) sched status: Thread 1: status =3D Runnable, associated_mx =3D 0x0, associated_cv =3D = 0x0 =3D=3D8435=3D=3D at 0x52BFF042: ??? valgrind: vg_memory.c:508 (vgPlain_find_map_space): Assertion `(addr & ((1 << 12)-1)) =3D=3D 0' failed. =3D=3D8435=3D=3D at 0xB002BD98: vgPlain_skin_assert_fail = (vg_mylibc.c:1169) sched status: Thread 1: status =3D Runnable, associated_mx =3D 0x0, associated_cv =3D = 0x0 =3D=3D8435=3D=3D at 0x52BFF042: ??? ---------------------------------------------------- I'm probably doing something wrong, but I'm stuck here at the moment. Problem is reliably reproducable and test works fine when running not under Valgrind. Machine is vanilla Mandrake 10 installation, Valgrind 2.1.2 is built from source using stock compiler. Firebird is the checkout from CVS HEAD a few days old, I may prepare testcase bundle if there is an interest. Any suggestions? Nickolay Samofatov |
|
From: Danny A. C. G. <val...@bi...> - 2004-08-20 00:06:43
|
=2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi,=20 Im new user of Valgrind, and I dont know how to read his output.. anybody= =20 can explain what is a "Invalid read of size X" .. and can describe where i= s=20 my error here (im gettin lots of these erros.. lol): =3D=3D2961=3D=3D Invalid read of size 4 =3D=3D2961=3D=3D at 0x804EE29: C3D_Core_c::siFindCoreModulePosByType(uns= igned)=20 const (core.cpp:487) =3D=3D2961=3D=3D by 0x804EBDD: C3D_Core_c::hRegisterModule(C3D_ICoreModu= le_c*)=20 (core.cpp:407) =3D=3D2961=3D=3D by 0x804EA48: C3D_Core_c::Create() (core.cpp:232) =3D=3D2961=3D=3D by 0x804E33B: C3D_Core_c::C3D_Core_c() (core.cpp:59) =3D=3D2961=3D=3D Address 0x1C0BEE98 is 0 bytes inside a block of size 40 f= ree'd =3D=3D2961=3D=3D at 0x1B902616: operator delete(void*) (vg_replace_mallo= c.c:156) =3D=3D2961=3D=3D by 0x80796BA: C3D_MovementManager_c::~C3D_MovementManag= er_c()=20 (movementmanager.cpp:16) =3D=3D2961=3D=3D by 0x804F241:=20 C3D_SingletonBase_c<C3D_MovementManager_c>::pclCreate() (singleton.h:34) =3D=3D2961=3D=3D by 0x804EA30: C3D_Core_c::Create() (core.cpp:232) Thanks =09 =2D --=20 Danny Angelo Carminati Grein Diretor de T.I. Bitcrafters Inc. =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBJRZw3bTZQYPv0SMRAt3sAKCdDjde+j1rKWWYUxTpVVP58zUeXACffBba v4OibERi51x66suQIHB6kMM=3D =3DYDyH =2D----END PGP SIGNATURE----- |
|
From: Tom Hu <to...@ci...> - 2004-08-19 22:07:38
|
This is very simple error. The error looks like it does not like my file
format:
x> valgrind --tool=memcheck --suppressions=/users/tomhu/log5.supp
./my_program
==4293== Memcheck, a memory error detector for x86-linux.
==4293== Copyright (C) 2002-2004, and GNU GPL'd, by Julian Seward.
==4293== Using valgrind-2.1.1, a program supervision framework for
x86-linux.
==4293== Copyright (C) 2000-2004, and GNU GPL'd, by Julian Seward.
==4293== FATAL: in suppressions file: `/users/tomhu/log5.supp': syntax
error on: {
==4293== exiting now.
My syppression file /users/tomhu/log5.supp:
#
#
{
__memcpyy
Memcheck:Cond
fun:memcmp
fun:ikev2_sa_compare
fun:avl_search
fun:wavl_search
}
{
__memcpyy2
Memcheck:Cond
fun:ikev2_sa_compare
fun:avl_search
fun:wavl_search
fun:ikev2_find_sa
}
Thanks
Tom Hu
|
|
From: Paul M. <pau...@ce...> - 2004-08-19 15:48:38
|
(vg 2.1.2 on redhat 9) code does =20 int state; rc =3D pthread_setcancelstate(PTHREAD_CANCEL_DISABLE, &state); assert(rc =3D=3D 0); if (state =3D=3D PTHREAD-CANCEL_ENABLE) .... =20 valgrind says the the if state =3D=3D line depends on an unitialized = memory location. If I attach gdb at that point then yes state contains junk. setcancelstate has not set it When I try to isolate this into a small piece of code it works fine - so I cannot send a simple repro case If I set state =3D 0 before the call to cancel state it also stop vg complaining but the value is still not being set bt the call. The code is inlined in a cpp header file - i dont know if thats a useful clue or not. |
|
From: Nicholas N. <nj...@ca...> - 2004-08-19 15:15:32
|
On Thu, 19 Aug 2004, pkr wrote: > 1. Wanted to know if it is possible to make memcheck work too, > as somebody mentioned using 0xa0000000. Not as it stands with your machine's 2G/2G user/kernel memory layout, sorry. N |
|
From: Tom H. <th...@cy...> - 2004-08-19 14:54:11
|
In message <412...@ya...>
pan...@ya... wrote:
> 2. Is it possible for valgrind to generate its report on some other
> event apart from program exit ? ie I have a daemon which is up 24x7 and
> would like to collect the valgrind report at specific time intervals.
Memory access problems are reported as they happen. Memory leaks are
reported on exit or when the VALGRIND_DO_LEAK_CHECK client request is
used by the target program.
Tom
--
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/
|
|
From: pkr <pan...@ya...> - 2004-08-19 14:29:55
|
Hi, Sorry to come back again after a long time. 2 queries this time.. 1. Wanted to know if it is possible to make memcheck work too, as somebody mentioned using 0xa0000000. 2. Is it possible for valgrind to generate its report on some other event apart from program exit ? ie I have a daemon which is up 24x7 and would like to collect the valgrind report at specific time intervals. Thanks, Pankaj Nicholas Nethercote wrote: > On Thu, 5 Aug 2004, pkr wrote: > >> 2 pieces of info. >> 1. As Nick guessed earlier, the kernel is configured for 4GB and >> 2GBuser/2GB kernel . >> >> Let me know if there could be a fix from valgrind. > > > Try this: > > - in coregrind/stage1.c, change "info.mapbase" on line 181 from 0xb1000000 > to 0x71000000. > > - in coregrind/Makefile, change "kickstart_base" from 0xb0000000 to > 0x70000000. > > - re-make Valgrind > > I found that Memcheck and Helgrind do not work under this setup, because > they cannot load libraries at 0x40000000 as they want to -- the tools > reserve too much of the 2GB address space for themselves. > > However, Addrcheck, Cachegrind and Massif do work, as they need less > space for themselves, which is a start. Note that if you try running > big programs under Valgrind, you might run out of memory, as the system > doesn't have that much to play with. > > It really would be nice to improve on this situation. > > N > > > ------------------------------------------------------- > This SF.Net email is sponsored by OSTG. Have you noticed the changes on > Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, > one more big change to announce. We are now OSTG- Open Source Technology > Group. Come see the changes on the new OSTG site. www.ostg.com |
|
From: Tom H. <th...@cy...> - 2004-08-19 11:40:24
|
In message <1092912347.30028.18.camel@localhost.localdomain>
Rajesha TS <raj...@hp...> wrote:
> my work environment is :
> Linux Fedora 2
> Intel Pentium 4
>
> i installed the valgrind without any serious message ...
>
> as per instruction, when i execute valgrind for testing purpose, as,
> /usr/bin/valgrind ls -l
> it gave me the following error message :
> "ls: error while loading shared libraries:
> /usr/local/lib/valgrind/libpthread.so.0: undefined symbol:
> __libc_connect"
Use a more recent version of valgrind and this problem will go away.
Tom
--
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/
|
|
From: Rajesha TS <raj...@hp...> - 2004-08-19 10:49:02
|
hi all, i just now introduced to valgrind ... i downloaded valgrind-2.0.0 source tree and compiled as per the instruction... my work environment is : Linux Fedora 2 Intel Pentium 4 i installed the valgrind without any serious message ... as per instruction, when i execute valgrind for testing purpose, as, /usr/bin/valgrind ls -l it gave me the following error message : "ls: error while loading shared libraries: /usr/local/lib/valgrind/libpthread.so.0: undefined symbol: __libc_connect" can anybody pls help me to solve this ? with lot of thanx in adv., -- Rajesha TS <raj...@hp...> HP Labs India |