Lines Matching full:programs
15 analyse 64-bit programs running on z/Architecture. Most user space
57 errors) in programs doing vector saturated narrowing instructions.
330 255355 helgrind/drd: crash on threaded programs doing fork
419 bare minimum SSE4 instructions to needed to run programs on Mac OS X
517 * Support for analyzing programs running under Wine with has been
520 Windows-programs compiled with MinGW or one of the Microsoft Visual
547 249435 Analyzing wine programs with callgrind triggers a crash
729 - 32-bit programs on x86 and AMD64 (a.k.a x86-64) machines are supported
730 fairly well. For 10.5.x, 32-bit programs are the default even on
731 64-bit machines, so it handles most current programs.
733 - 64-bit programs on x86 and AMD64 (a.k.a x86-64) machines are not
734 officially supported, but simple programs at least will probably work.
760 - Threaded programs may run more slowly than on Linux.
917 requires a lot of memory and can be very slow in programs that
1056 * For people who use Valgrind with MPI programs, the installed
1079 false errors even in simple programs. Helgrind and DRD may also
1498 n-i-bz Massif/Cachegrind output corruption when programs fork
1581 - Scalability improvements for very large programs, particularly those
1584 faster for all programs, with x86-linux seeing the largest
1728 151209 V unable to execute programs for users with UID > 2^16
1861 bugs were causing large programs to segfault with --tool=callgrind and
1892 132146 Programs with long sequences of bswap[l,q]s
1955 This means you should be able to run programs that use more memory
1983 this supports programs using to 32G of address space. On 64-bit
2195 result, Valgrind should be much more robust with programs that use
2199 space available to user programs (usually 3GB or 4GB) can be fully
2255 format. This is designed to make it easy for other programs to
2429 small programs, but it's a start. Many thanks to Paul Mackerras for
2438 Without PIE enabled, AMD64 programs will only be able to access 2GB of
2443 - Support for programs that use stack-switching has been improved. Use
2448 - Support for programs that use self-modifying code has been improved,
2449 in particular programs that put temporary code fragments on the stack.
2450 This helps for C programs compiled with GCC that use nested functions,
2451 and also Ada programs. This is controlled with the --smc-check
2460 - Programs that allocate many heap blocks may run faster, due to
2470 more slowly than the old one, so programs may take longer to start.
2472 started, programs should run at about the same speed. Feedback about
2480 - There is a subtle change to the way exiting of threaded programs
2491 use valgrind for debugging MPI-based programs. The relevant
2542 106283 PIE client programs are loaded at address 0
2691 96520 All programs crashing at _dl_start (in /lib/ld-2.3.3.so) ...
2925 be possible for client programs to allocate over 800MB of
3010 75099 impossible to trace multiprocess programs
3017 75614 using -gstabs when building your programs the `impossible' happened
3024 72781 Cachegrind crashes with kde programs
3041 70827 programs with lots of shared libraries report "mmap failed"
3096 to 300k average bbs. Programs on the size of OOo (680m17) are
3253 various problems that 1.9.6 has with threaded programs
3263 resolver functions in threaded programs, 20030716 should improve
3294 some SSE based programs may work. Currently you need to specify
3357 usually manifested by threaded programs deadlocking in system calls,
3376 good enough to keep alive programs which previously died for lack of
3420 this, and so 1.9.5 works on RH9. Threaded programs still work,
