> One thing that I'd like to ask at this point is: what level of support for
> Solaris should we say there is, in the release announcement? Now that we
> unfortunately no longer have a Solaris maintainer, I am concerned that could
> wind up shipping a non-working Solaris port. A similar question
You should not need to build 32-bit Valgrind explicitly.
By default Valgrind on newer Solaris should handle both 32-bit and
64-bit programs; but see README.solaris for caveats.
You did not specify Solaris version (pkg info entire) so it is hard to
say where you are.
Note that Solaris 11.1 and 11.2
Il giorno lun 19 nov 2018 alle ore 16:53 David Faure ha scritto:
>
> When using vgdb (e.g. `valgrind --vgdb-error=0 myprog`)
> and there's a valgrind warning for an uninitialized read, on a line like
> if (a || b)
>
> The question that happens then is, of course, was it a or b that was
> unini
Il giorno lun 18 giu 2018 alle ore 15:57 Alan Corey
ha scritto:
>
> Um, dumb question probably but you checked it in where? Looks like
> there are at least 4 forks of Valgrind on Github, on sourceware.org I
> just see releases, nothing since 3.13.
In addition to Tom's answer: I found at least 20
Dear Valgrind'ers,
I have been maintaining the Valgrind Solaris (and partly also illumos)
port for nearly three years,
ensuring it builds and runs on the latest Solaris 11.1, 11.2, 11.3
(and 11.4 until April 2018).
I have been co-developing the port since 2013.
I have had a pleasure to meet and wo
2018-02-16 17:27 GMT+01:00 John Reiser :
>> What would you like to do instead? REOPENED?
>
>
> The presenting symptom is the same, so REOPENED is an obvious candidate.
> My post was to draw attention to the re-appearance because I
> could not change the Status away from "no need to look at this any
2018-02-23 19:54 GMT+01:00 SILVA João :
> The reason we allocate everything statically is safety.
>
> What about you, Ivo, any other hints on creating space for this executable?
Unfortunately I have run out of ideas, I am sorry.
>
> This seems a limitation of Valgrind, should I create a bug repor
2018-02-21 22:55 GMT+01:00 John Reiser :
> On 02/19/2018 09:35 UTC, Ivo Raisr wrote:
>
>> I'd prefer another bug report in this case.
>> Although the symptoms are equivalent, the underlying reasoning is
>> different.
>> And the new bug will have diffe
2018-02-15 15:54 GMT+01:00 John Reiser :
>> --18142-- WARNING: Serious error when reading debug info
>> --18142-- When reading debug info from
>> /export/home/paulf/tools/gcc/lib/libstdc++.so.6.0.25:
>> --18142-- Can't make sense of .rodata section mapping
>>
>> (GCC SVN head, Solaris 11.3, Valgrin
2018-02-12 16:27 GMT+01:00 Mark Wielaard :
> Hi,
>
> The experimental sgcheck tool is in a pretty bad state. On some systems
> it doesn't even run a simple /bin/true program because it doesn't
> support guarded loads/stores. It is also the only tool which really
> uses some of the debuginfo var/typ
2018-02-11 22:17 GMT+01:00 Paul Floyd :
>
>
>> On 11 Feb 2018, at 21:36, John Reiser wrote:
>>
>>> --18142-- WARNING: Serious error when reading debug info
>>> --18142-- When reading debug info from
>>> /export/home/paulf/tools/gcc/lib/libstdc++.so.6.0.25:
>>> --18142-- Can't make sense of .rodat
2018-01-24 1:36 GMT+01:00 Wuweijia :
> Hi:
> But I can not access the git of valgrind. Is there any way to get the
> newest source code; Maybe the network configuration do not allow it;
It is hard to help you without any specific error shown.
If this is indeed a network configuration, the
2018-01-23 12:27 GMT+01:00 Wuweijia :
> Hi
> Thanks for your advise. You mean I need to download valgrind 3.13. and
> merge your commit, compile it.
Actually not.
I meant you should build Valgrind from source code as per instructions
at: http://valgrind.org/downloads/repository.html
I.
--
2018-01-23 4:02 GMT+01:00 Wuweijia :
> Hi
>
> I ran the program with mem-check, 99% is okay, it will not
> last long. But sometimes it last very long, at least one hour in one
> function. And then I add the –trace-signals=yes to find what it happen.
> Valgrind show me some signal happ
2017-12-08 22:18 GMT+01:00 Rob Boehne :
> All,
>
> I built valgrind 3.13.0 from source with prefix=/opt/valgrind-3.13 and
> installed there on a 64-bit Intel Solaris machine.
> It seems to work well for the program passed on the command line, but
> tracing children doesn’t.
>
> Whenever I pass –tra
2017-12-05 11:42 GMT+01:00 Silva João :
> Hi,
>
> I was able to build Valgrind and run the program with value 0x7d00:
>
>valt_load_address_pri_norml="0x7d00"
>valt_load_address_pri_norml="0x7d00"
>valt_load_address_pri_norml="0x7d00"
>
We have extended the submission deadline for proposals until 6th December.
Kind regards,
Ivo Raisr
2017-10-13 12:37 GMT+02:00 Ivo Raisr :
> Debugging Tools developer room at FOSDEM 2018
> (Brussels, Belgium, February 3th).
>
> FOSDEM is a free software event that offers open source c
2017-11-29 19:04 GMT+01:00 Silva João :
>> I have no idea why this file wants to allocate ~1,7 GB of bss.
>
> All memory is allocated statically in Ada/SPARK. There is no dynamic memory
> allocation except for the usage of libxerces in C/C++.
BSS is statically "allocated" memory.
>
>> You can wo
2017-11-29 17:55 GMT+01:00 Silva João :
> This is the result of readelf -l:
...
> Program Headers:
> Type Offset VirtAddr PhysAddr
> FileSizMemSiz Flags Align
> PHDR 0x0040 0x00400040 0x
2017-11-29 17:15 GMT+01:00 Silva João :
> I'm not sure it worked (I was already using Valgrind that I built, so I
> patched, ran make and make install):
It worked pretty well.
Valgrind tries to map an ELF file (/u/wh/rel/ifaplrel/pw_fwp_engine.eab)
and one of its program headers has two parts: d
Thank you for a quick reply.
The error message observed is actually what check_mmap() in
coregrind/m_ume/elf.c reports.
I suspect that we run into issue with VG_(am_get_advisory)() but I want to be
sure.
Please could you grab Valgrind source, apply the attached patch to it
and build it as per http
2017-11-29 13:37 GMT+01:00 Silva João :
> valgrind: mmap(0xa64000, 1793339392) failed in UME with error 22 (Invalid
> argument).
This may be caused by other mmap arguments than just size.
Please report some details about your system and also strace output
for the valgrind run.
Particularly intere
room day: Saturday 3 Feb 2018
Hope to see you all at FOSDEM 2018 in the joint Debugging Tools devroom.
Brussels (Belgium), Saturday February 3th 2018.
On behalf of the devroom committee,
Ivo Raisr
---
>> Sparc is not, and never has been, a supported platform. The list of
>> supported platforms can be found here:
>>
>>http://valgrind.org/info/platforms.html
>>
>> Note at the bottom that there are details of an out of tree attempt at a
>> port, but there is no support in the main valgrind rele
2017-09-23 9:01 GMT+02:00 Julian Seward :
>
> On 19/09/17 20:19, John Reiser wrote:
>>> Can someone who has worked on the code clarify if Valgrind is in fact
>>> expected to work on an ARMv5?
>
> ARMv5 and ARMv6 aren't supported.
In that case we need to update http://www.valgrind.org/info/platform
Dear developers,
Would the Valgrind community be interested in a Valgrind developer
room at FOSDEM 2018 [1]?
The deadline for developer room proposals is September 20th.
I volunteer to help with the organization, similarly to the last year.
We had a dev room at FOSDEM 2014, 2015, and 2017 and it s
2017-08-17 20:38 GMT+02:00 Rob Boehne :
> Category: Meta Packages/Incorporations
>
> State: Installed
>
> Publisher: solaris
>
> Version: 0.5.11 (Oracle Solaris 11.3.21.5.0)
>
> Build Release: 5.11
>
>Branch: 0.175.3.21.0.5.0
>
>Packaging
2017-08-17 18:42 GMT+02:00 Rob Boehne :
> All,
>
> Is there a guide for building valgrind on intelsolaris?
> ...
> Is there a list of prerequisites somewhere?
>
Yes, there is. README.solaris.
I.
--
Check out the vibrant t
2017-08-17 18:42 GMT+02:00 Rob Boehne :
> All,
>
> Is there a guide for building valgrind on intelsolaris? I’m running into
> an explict error
>
> *valgrind-3.13.0/include/vki/vki-solaris-repcache.h:343:2:* *error: *#error
> Unsupported repcache protocol version
>
>
Rob,
You are not missing a p
Dear Valgrind users and developers,
Valgrind source code repository has been migrated today successfully
from Subversion
to git SCM at sourceware.org. Valgrind www pages has been updated as well
to reflect new situation.
Repositories "valgrind" and "vex" should be treated as read-only from now on
2017-08-05 1:13 GMT+02:00 Mark Wielaard :
> On Fri, 2017-08-04 at 21:58 +0200, Mark Wielaard wrote:
>
>> > How the test migration was performed:
>> > ~~
>> > See recipes at https://github.com/ivosh/valgrind-git-migration
>>
>> I'll follow that to recreate the git reposit
Dear Valgrind community,
I am happy to announce that migration of Valgrind sources from
existing Subversion SCM to modern git SCM will happen 14th August
2017.
What is going on now?
~
The migration has been tested and all infrastructure is in place now.
We still use the official S
2017-08-02 20:01 GMT+02:00 Lionel Cons :
> On 2 August 2017 at 18:26, Ivo Raisr wrote:
>> Dear Valgrind users,
>>
>> Please if you know of any users interested in sparc64/Linux or
>> sparc64/Solaris Valgrind ports, let me know. We would like to
>> determine how
Dear Valgrind users,
Please if you know of any users interested in sparc64/Linux or
sparc64/Solaris Valgrind ports, let me know. We would like to
determine how much time and effort to put into developing and
maintaining them further in a foreseeable future.
More information here:
http://valgrind.
An interesting article:
https://blog.regehr.org/archives/1520
If the long list of undefined behaviours starts getting boring or
horrifying, then skip to the nice and concise "Summary" section for
soothing words of consolation, and the actionable countermeasures.
I.
--
2017-07-07 9:58 GMT+02:00 Mark Wielaard :
> On Thu, 2017-07-06 at 08:05 -0700, John Reiser wrote:
>> On 07/06/2017 @1457Z, Mark Wielaard wrote:
>> > On Thu, 2017-07-06 at 13:24 +, Phil Longstaff wrote:
>> >> Where can I find source tarballs for 3.11.0 and 3.12.0?
>> >
>> > http://valgrind.org/d
2017-06-28 4:40 GMT+02:00 Alberthus :
> Yes, that's the idea.
> It is a problem i had quite often in the beginning, I searched on the
> internet and also could'n find a solution. I ended up finding it by chance
> when I was searching for something else.
> When I first read about vgdb I thought, "wh
2017-06-21 18:51 GMT+02:00 Bart Van Assche :
> Regarding the workflow of kernel maintainers: some use mutt as e-mail
> client. Others use a GUI e-mail client and use patchwork for managing
> patches. Patchwork is a server that picks up patches and patch series
> from Linux kernel related mailing li
2017-06-23 9:50 GMT+02:00 Wuweijia :
> hg_intercepts.c:97:61: note: in definition of macro 'PTH_FUNC'
>
> ret_ty I_WRAP_SONAME_FNNAME_ZZ(VG_Z_LIBPTHREAD_SONAME,f)(args); \
>
> ^
>
> hg_intercepts.c:1644:10: error: unknown type name 'p
2017-06-21 4:05 GMT+02:00 Bart Van Assche :
> On 06/16/17 08:17, Ivo Raisr wrote:
>>
>> What will be my simple workflow in new git SCM?
>> ~~
>> Not much will be changed from the way we worked in SVN.
>> We still prepare pa
2017-06-09 21:55 GMT+02:00 Alberthus via Valgrind-users
:
> Hello,
> I'm new to programing and have been learning how to debug my program with
> gdb and find leaks with valgrind, and have been trying to do them both
> together using the instructions described in section 3.2 of
> http://valgrind.org
Dear Valgrind community,
Now that Valgrind release 3.13.0 is out, we are pleased to announce
an imminent migration of Valgrind sources from existing Subversion SCM
to modern git SCM, as discussed during our FOSDEM 2017 Valgrind devroom
and announced publicly back at the end of February 2017.
What
2017-06-10 12:57 GMT+02:00 Julian Seward :
> On 02/06/17 17:57, Julian Seward wrote:
>> An RC1 tarball for 3.13.0 is now available at [..]
>
> Thank you to everybody who tried out the RC1 tarball. There's now
> an RC2 available for testing at
>
> ftp://sourceware.org/pub/valgrind/valgrind-3.13.0.R
2017-05-29 13:20 GMT+02:00 FEVOTTE Francois :
> Dear Valgrind developers,
>
> first, please forgive us if this post is out of place in this list.
>
> We would like to introduce Verrou [1], a floating-point error diagnostics
> tool based on Valgrind. The idea behind the tool is that it replaces all
2017-05-08 20:39 GMT+02:00 Siddharth Nilakantan :
> Hi Mike and Ivo,
>
> I noticed a thread where you guys had a discussion going.
>
> https://sourceforge.net/p/valgrind/mailman/message/35687503/
>
> I was playing around with writing a tool that does some online analysis of
> register reads/writes.
2017-03-08 11:56 GMT+01:00 Julian Seward :
> On 08/03/17 07:16, A. Lester Buck III wrote:
>> I don't understand the last line:
>>
>> Address 0xf95f6a0 is in the BSS segment of /usr/local/lib/libaws-cpp-\
>> sdk-core.so
>
> What this means is, the address that has been passed to free -- that is,
> 0
2017-02-24 20:21 GMT+01:00 Ivo Raisr :
> Dear Valgrind community,
>
> We are pleased to announce an imminent migration of Valgrind sources
> from existing Subversion SCM to modern git SCM, as discussed during
> our FOSDEM 2017 Valgrind devroom.
So far a number of very useful com
2017-03-03 0:01 GMT+01:00 Mike Lui :
> I did a poor job explaining my inquiry. I'm writing a valgrind tool that's
> tracking the IOPS/FLOPS/reads/writes reported by VEX IR during
> instrumentation, and doing some minor analysis on the IR with a
> instrument_basic_block callback (as documented in
>
2017-03-02 23:07 GMT+01:00 Mike Lui :
> Hi Ivo,
>
> I didn't get a response, but I found a snippet in the original paper:
> https://www.cs.columbia.edu/~junfeng/09fa-e6998/papers/valgrind.pdf
>
> Table 1 says these functions are only for syscalls and the valgrind core. Is
> that still correct?
Hi
2017-02-25 3:55 GMT+01:00 Mike Lui :
> Being unable to search through gmane for now, I turn to the users group.
>
> I'd like some clarification regarding some functions I'm seeing in the tool
> interface.
>
> track_new_mem_startup
>
> track_new_mem_mmap
> ...
> track_pre_mem_read
> track_pre_m
2017-02-27 21:45 GMT+01:00 Matthias Schwarzott :
>
> I wonder if the parameter 10 in --abbrev=10 should be skipped, now that
> git has an automatic estimation for the number of digits to be used.
Are you referring to "--short=10" command line option for "git rev-parse"?
The manual [1] states that
2017-02-28 23:13 GMT+01:00 Tom Hughes :
> On 28/02/17 20:56, Ivo Raisr wrote:
>
>> So we decided to stick with existing (SVN) workflow which translates to
>> "rebased branches at the top of the tree".
>> Our valgrind.git config will have (after the final
2017-02-28 22:16 GMT+01:00 Christian Borntraeger :
> The given workflow requires that there is no other push between the pull
> and the push. If for some reason somebody else pushes some update after
> you have commited, you can recover with a rebase. There is a nice combine
> of pull + rebase:
> g
2017-02-27 10:02 GMT+01:00 Christian Borntraeger :
> For a pull like approach I would suggest to either
> a: do not this step (Linux style git handling)
> b: use git pull --rebase (flat history style)
>
>
>> build + test
>> git commit
>> [git push - if you have write access]
>
> If we give write ac
2017-02-28 8:52 GMT+01:00 James Orr :
> I believe this is a known issue with MacOSX Sierra.
Patches are welcome!
I.
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! htt
2017-02-26 9:08 GMT+01:00 Austin English :
> On Sun, Feb 26, 2017 at 1:35 AM, Austin English
> wrote:
> Assuming leaving git broken until the migration is okay (which seems
> fine, given that it currently is and I'm decently sure I'm the only
> person using this ;) ), here's a patch that works fo
2017-02-26 6:04 GMT+01:00 Austin English :
> Indeed, svn related commands must be replaced with git ones.
> Can you propose a patch? I assume instead of SVN revisions
> we need to get git commit ids.
> I will have a look at the other Valgrind parts.
>
> Yeah, I'll look this week probably.
>
> Had
2017-02-25 1:53 GMT+01:00 Austin English :
> Hi Ivo,
>
> I'm very excited for the git move! I tested for
> https://bugs.kde.org/show_bug.cgi?id=352395, which I rely upon to keep
> track of precisely which version of Valgrind I'm testing with
> (especially useful for historical logs).
>
> With git,
Dear Valgrind community,
We are pleased to announce an imminent migration of Valgrind sources
from existing Subversion SCM to modern git SCM, as discussed during
our FOSDEM 2017 Valgrind devroom.
What is going on now?
~
The migration has just started. We are now in beta testing st
2017-01-13 22:27 GMT+01:00 Dan Shelton :
> On 13 January 2017 at 21:59, Julian Seward wrote:
> >
> > That's not a fair comparison. The Solaris port has a very active
> > maintainer and (presumably) also has users.
>
> Well, given that Mr Irek was part of the Opensolaris community I THINK
> he wa
2017-01-13 21:43 GMT+01:00 Irek Szczesniak :
> OK, next is to remove the Solaris port of valgrind. OS was
> discontinued, Oracle does not respond to emails and there is no
> emulator.
You can say remove OS X port of Valgrind as well in this manner.
Prove your statements.
Who says "[Solaris] OS
2017-01-12 20:36 GMT+01:00 Philippe Waroquiers <
philippe.waroqui...@skynet.be>:
> On Thu, 2017-01-12 at 13:37 +0100, Roland Mainz wrote:
> > On Thu, Jan 12, 2017 at 1:31 PM, Petar Jovanovic
> wrote:
> > > On Wed, Jan 4, 2017 at 3:21 PM, Philippe Waroquiers
> > > wrote:
> > >> No sign of any til
2017-01-05 12:54 GMT+01:00 Matthias Apitz :
>
> Hello,
>
> I'm 'valgrinding' a huge client/server application, where the server
> runs on Linux (SLES 12) and uses SSL (OpenSSL) to communicate with the
> clients.
>
> Valgrind is complaining a lot on any SSL function call (some 20.000
> lines) befor
2016-12-08 11:28 GMT+01:00 Radoslaw Kujawa :
>
> W dniu 08.12.2016 o 11:12, Ivo Raisr pisze:
>
>
>
> 2016-12-07 13:54 GMT+01:00 Radoslaw Kujawa :
>
>> Hi Ivo,
>>
>> here is the log that appeared when we switched on trace-syscalls:
>>
>> SYSCALL[
2016-12-07 18:39 GMT+01:00 Gregory Czajkowski :
> I have processes near 256GB, need to run valgrind to determine why, but it
> runs out of memory ~60GB
>
>
> ==15336== Valgrind's memory management: out of memory:
>
> ==15336==newSuperblock's request for 4194304 bytes failed.
>
> ==1533
2016-12-07 13:54 GMT+01:00 Radoslaw Kujawa :
> Hi Ivo,
>
> here is the log that appeared when we switched on trace-syscalls:
>
> SYSCALL[28094,1](89) sys_readlink ( 0x374581b667(/proc/self/exe),
> 0xffeffec10, 4096 ) --> [pre-success] Success(0x52)
> valgrind: m_syswrap/syswrap-main.c:1938 (vgPlai
2016-12-06 15:39 GMT+00:00 Radoslaw Kujawa :
> Hi everyone,
>
> we're trying to run valgrind on a multi-threaded binary that uses fuse to
> emulate a filesystem. We've found --sim-hints=fuse-compatible flag, which is
> great (resolves some problems with deadlocks), but then valgrind fails on an
A gentle reminder to all Valgrind folks:
we call for your participation at FOSDEM 2017, see below.
The deadline for abstract submissions is in less than two weeks.
Let us know if you have something in works and need slightly
more time.
See you all there,
I.
---
Val
2016-10-19 22:56 GMT+02:00 Ivo Raisr :
>
>
> 2016-10-19 19:41 GMT+02:00 Rob Boehne :
>
>> Hello Ivo,
>>
>> I attempted a fresh hg checkout and build of valgrind-solaris, ran “bash
>> autogen.sh” ./configure CC=“gcc –m64” CXX=“g++ -m64” and gmake, but it died
&
2016-10-19 19:41 GMT+02:00 Rob Boehne :
> Hello Ivo,
>
> I attempted a fresh hg checkout and build of valgrind-solaris, ran “bash
> autogen.sh” ./configure CC=“gcc –m64” CXX=“g++ -m64” and gmake, but it died
> down in VEX in assembly:
>
> gcc -m64 -DHAVE_CONFIG_H -I. -I.. -I.. -I../include -I../V
Valgrind developer room at FOSDEM 2017 (Brussels, Belgium, February 4th).
FOSDEM is a free software event that offers open source communities a
place to meet, share ideas and collaborate. It is renown for being
highly developer-oriented and brings together 5000+ hackers from all
over the world.
2016-10-06 22:27 GMT+02:00 Patrick J. LoPresti :
> On Thu, Oct 6, 2016 at 8:53 AM, Alex Bligh wrote:
> >
> >
> > > On 6 Oct 2016, at 16:06, Mateusz Jemielity <
> m.jemiel...@is-wireless.com> wrote:
> > >
> > > The effects are equivalent to pthread_rwlock_init, thus in my opinion
> they
> > > requ
2016-08-30 14:41 GMT+02:00 John Reiser :
> > is it possible to detect all calls of some specific function in the code
> with Callgrind?
> >
> > Let's say I have some project and I know, that there's function
> SparseSolver() used several times and I need to know where specifically
> (caller functi
2016-07-26 15:53 GMT+02:00 Rob Boehne :
> As I’ve found valgrind quite useful on x86/Linux for many years, I was
> very excited to see a project to support Solaris Sparc, and I’d love to
> have this available, as I maintain a large, old codebase with a pool
> allocator (Electric Fence doesn’t deal
2016-06-18 11:19 GMT+02:00 Jeffrey Walton :
> Hi Everyone,
>
> I downloaded, built and installed the latest Valgrind from sources.
> There were no special config options - just './config' (IIRC). After
> installation I deleted Valgrind source and build directory.
>
> I'm experiencing the following
2016-06-09 15:24 GMT+02:00 Kirill Frolov :
> Hello, All!
>
> How can I annotate source code (see below) to stop valgrind's DRD
> tool complain about data race?
>
>I think this source doesn't contain any data race, but DRD thinks
> otherwise. This is because common synchronization primitiv
> > > +99.95% (84,704B) (heap allocation functions) malloc/new/new[],
> > > --alloc-fns, etc.
> > > +->85.79% (72,704B) 0x: ??? (in /usr/lib64/libstdc++.so.6.0.21)
> > > +| ->85.79% (72,704B) 0x: call_init.part.0 (dl-init.c:72)
> > > +| ->85.79% (72,704B) 0x: _dl_init (dl-
Hi there,
Thank you for analysing the situation.
Let me clarify things a bit...
2016-04-15 2:56 GMT+02:00 John Reiser :
> =
> memcheck/tests/leak_cpp_interior/leak_cpp_interior.stderr.diff-64bit
> (stderr)
> - still reachable: 239 bytes in 8 blocks
> + still reachable: 72,943 bytes in 9 b
2016-03-30 10:59 GMT+02:00 David Faure :
> This simple testcase :
>
> int foo() {
> struct Foo {
> int *i;
> Foo() { i = new int(42); }
> };
> static Foo f;
> return *(f.i);
> }
>
> called from two threads (
> http://www.davidfaure.fr/2016/testcase_ogoffart.cpp)
>
2015-12-11 14:01 GMT+01:00 yoma sophian :
> hi Phillippe:
>
> 2015-12-11 6:42 GMT+08:00 Philippe Waroquiers <
> philippe.waroqui...@skynet.be>:
> > On Mon, 2015-12-07 at 00:05 +0100, Philippe Waroquiers wrote:
> >> I think there is a bug in the massif logic to make a peak detailed
> >> snapshot at
2015-10-19 23:04 GMT+02:00 Paul Floyd :
>
> On 19 Oct 2015, at 20:25, Matthew Wozniczka wrote:
>
> X86/Solaris is listed as supported @
> http://valgrind.org/info/platforms.html, so I grabbed a copy of
> valgrind-3.11.0.tar.bz2 and followed the instructions @
> http://valgrind.org/docs/manual/dist
2015-10-19 20:34 GMT+02:00 Matthew Wozniczka :
> X86/Solaris is listed as supported @
> http://valgrind.org/info/platforms.html, so I grabbed a copy of
> valgrind-3.11.0.tar.bz2 and followed the instructions @
> http://valgrind.org/docs/manual/dist.install.html, but I got the
> following error whe
2015-09-08 1:35 GMT+02:00 Yue Chen :
> I tried to use Valgrind syscall tracing utility on FreeBSD 10.1. I found
> that that the results of ``truss'' and ``valgrind --trace-syscalls=yes''
> are a little different. For example, the result of Valgrind has extra
> syscalls like sys_sysctl, sys_fstatfs
2015-07-13 19:17 GMT+02:00 Mikhail Baikov :
> Hello.
> Is there a possibility to disable signals handling by valgrind? The core
> will be created by the system and that will solve the problem.
>
This is not an option.
Run of your program (guest) is simulated by Valgrind (host).
Therefore Valgrin
2015-01-02 2:21 GMT+01:00 John Reiser :
>
> If there is any doubt [you have at least 1% doubt] then you should replace
> all uses
> of sprintf with snprintf instead. Using snprintf is not a fool-proof
> cure-all.
> If the length limit is reached then the result has no terminating '\0',
> so subse
85 matches
Mail list logo
