On Feb 19, 2008 10:09 PM, Nicholas Nethercote <[EMAIL PROTECTED]> wrote:
> But programmers should know in advance which bits of memory should be
> shared. Perhaps some client requests could be used which say "this section
> of memory will be shared" or "this section of memory won't be shared" coul
Nightly build on alvis ( i686, Red Hat 7.3 ) started at 2008-02-20 03:15:02 GMT
Results unchanged from 24 hours ago
Checking out valgrind source tree ... done
Configuring valgrind ... done
Building valgrind ... done
Running regression tests ..
Nightly build on lloyd ( x86_64, Fedora 7 ) started at 2008-02-20 03:05:06 GMT
Results unchanged from 24 hours ago
Checking out valgrind source tree ... done
Configuring valgrind ... done
Building valgrind ... done
Running regression tests ...
Nightly build on trojan ( x86_64, Fedora Core 6 ) started at 2008-02-20
03:25:21 GMT
Results unchanged from 24 hours ago
Checking out valgrind source tree ... done
Configuring valgrind ... done
Building valgrind ... done
Running regression tests
Nightly build on aston ( x86_64, Fedora Core 5 ) started at 2008-02-20 03:20:08
GMT
Results unchanged from 24 hours ago
Checking out valgrind source tree ... done
Configuring valgrind ... done
Building valgrind ... done
Running regression tests
Nightly build on dellow ( x86_64, Fedora 8 ) started at 2008-02-20 03:10:06 GMT
Results differ from 24 hours ago
Checking out valgrind source tree ... done
Configuring valgrind ... done
Building valgrind ... done
Running regression tests ... f
Nightly build on gill ( x86_64, Fedora Core 2 ) started at 2008-02-20 03:00:02
GMT
Results unchanged from 24 hours ago
Checking out valgrind source tree ... done
Configuring valgrind ... done
Building valgrind ... done
Running regression tests
> I've been doing some more experiments with helgrind and I would like
> to share some ideas...
Good. Some comments, in no particular order:
> Accuracy:
>
> The current default memory state machine (MSMHelgrind) gives too many
> false reports in presence of message queues, condvars, etc.
> So f
Author: sewardj
Date: 2008-02-20 01:12:54 + (Wed, 20 Feb 2008)
New Revision: 7428
Log:
Unbreak build on aix5.
Modified:
branches/DATASYMS/coregrind/Makefile.am
branches/DATASYMS/coregrind/m_debuginfo/d3basics.c
branches/DATASYMS/coregrind/m_debuginfo/debuginfo.c
branches/DATASYMS
> Is 'make html-docs' just supposed to work, or is there some unwritten
> stuff I need to do to get it to work?
It certainly just-works for me, but perhaps that's not robust over
different distros and which packages are installed. I just tried
on openSUSE 10.2 (amd64) and 10.3 (on ppc32) and it
I tried make html-docs from the docs/ directory but got network access
errors. I noticed that the --nonet option was used on the xsltproc
invocation, and some comment in the main Makefile that building the docs
is slow and intentionally left as the last thing to build. Was the
--nonet option
Author: sewardj
Date: 2008-02-19 22:03:01 + (Tue, 19 Feb 2008)
New Revision: 7427
Log:
When adding variables, line number info and unwind info to the various
tables in the DebugInfo (basically, any info that is associated with a
text address ranges), be more relaxed about the address ranges
ac
Author: sewardj
Date: 2008-02-19 21:11:13 + (Tue, 19 Feb 2008)
New Revision: 7426
Log:
Lots more tidying, and a bug fix.
* rename VG_(seginfo_start), VG_(seginfo_size),
VG_(seginfo_sym_offset) to VG_(seginfo_get_text_avma),
VG_(seginfo_get_text_size), VG_(seginfo_get_text_bias). This giv
On Tue, 19 Feb 2008, Konstantin Serebryany wrote:
> If we can ignore the majority of all memory accesses, we will speedup
> the whole thing.
> I have implemented the following:
> if ((address % X) != Y) we ignore this memory access.
> X and Y are command line parameters (% operation is optimiz
On Tue, 19 Feb 2008, Olivier Sarrouy wrote:
> Unhappily, i fall in trouble shadowing temporaries. For instance, if i
> want to trace an addition, how to obtain the content of t3 =
> Add32(Get::I32(0), Get::I32(6)), whithout manually shadowing all temps
> used in the SB ? In a nutshell, how to acce
Hello all,
I've been doing some more experiments with helgrind and I would like
to share some ideas...
The 'test' programs I've run have few things in common:
- Hundreds of threads.
- Heavy use of message queues, condvars, and other 'happens-before'
stuff. Mutexes are used as well.
- Strict timeo
Author: sewardj
Date: 2008-02-19 12:51:29 + (Tue, 19 Feb 2008)
New Revision: 7425
Log:
Make Dwarf3-based local variable descriptions work at least marginally
on ppc32/64-linux.
Modified:
branches/DATASYMS/coregrind/m_debuginfo/d3basics.c
branches/DATASYMS/coregrind/m_debuginfo/priv_d3
> I'd like to see the result of the operation Add32(Get::I32(0), Get::I32(6).
You should note that "Add32(Get::I32(0), Get::I32(6))" is not in
the flat-SSA form that will be sent to your tool. To see the
actual input to your instrumentation function, use
--trace-flags=0100 --trace-notbelow=
> Unhappily, i fall in trouble shadowing temporaries. For instance, if i
> want to trace an addition, how to obtain the content of t3 =
> Add32(Get::I32(0), Get::I32(6)), whithout manually shadowing all temps
> used in the SB ?
Not sure what you are asking. You want to see the value of t3, or
yo
Hi everyone,
I'm a french student using Valgrind framework to write a Redux-like
dataflow analyser to be used for intrusion detection.
I had initially planned to work from Redux Source Code but it's seems
too old to work with the latests versions of Valgrind, and hence i
decided to rebuild it
20 matches
Mail list logo
