On Sat, Apr 24, 2004 at 09:57:20PM +0100, Sérgio Monteiro Basto wrote:
> seems that I don't have any ~/.valgrindrc
>
> have someone one example of this file ?
You don't need a .valgrindrc. Just run
$ valgrind
To prove it, here's me excuting valgrind on the box in front of me:
$ ls -l ~/.valg
Ok valgrind have this
Available tools:
memcheck
addrcheck
cachegrind
corecheck
helgrind
massif
lackey
none
So I try
valgrind --tool=memcheck /usr/local/bin/foobillard >& debug2.txt
valgrind --tool=memcheck -v /usr/local/bin/foobil
Sérgio Monteiro Basto wrote:
On Sat, 2004-04-24 at 15:49, Brian Paul wrote:
When a program segfaults in free(), it's usually because of a memory
error (writing out of bounds, bouble-freeing a block, etc.).
valgrind will easily find such errors. Once you have it
built/installed, just run 'valgr
On Sat, 2004-04-24 at 15:49, Brian Paul wrote:
> When a program segfaults in free(), it's usually because of a memory
> error (writing out of bounds, bouble-freeing a block, etc.).
>
> valgrind will easily find such errors. Once you have it
> built/installed, just run 'valgrind myApplication' a
On Sat, 2004-04-24 at 15:49, Brian Paul wrote:
> When a program segfaults in free(), it's usually because of a memory
> error (writing out of bounds, bouble-freeing a block, etc.).
>
> valgrind will easily find such errors. Once you have it
> built/installed, just run 'valgrind myApplication' a
On Sat, 2004-04-24 at 00:14, Sérgio Monteiro Basto wrote:
> now debug.txt
>
> On Fri, 2004-04-23 at 15:06, Brian Paul wrote:
> > Felix Kühling wrote:
> > > I can reproduce this here too. I got a backtrace (see below) and took a
> > > look around s_linetemp.h. There is no INTERP_W for lines so the
Sérgio Monteiro Basto wrote:
now debug.txt
On Fri, 2004-04-23 at 15:06, Brian Paul wrote:
Felix Kühling wrote:
I can reproduce this here too. I got a backtrace (see below) and took a
look around s_linetemp.h. There is no INTERP_W for lines so the
assertion must fail for textured lines.
Don't wor
now debug.txt
On Fri, 2004-04-23 at 15:06, Brian Paul wrote:
> Felix Kühling wrote:
> > I can reproduce this here too. I got a backtrace (see below) and took a
> > look around s_linetemp.h. There is no INTERP_W for lines so the
> > assertion must fail for textured lines.
> >
> > Don't worry about
Felix Kühling wrote:
I can reproduce this here too. I got a backtrace (see below) and took a
look around s_linetemp.h. There is no INTERP_W for lines so the
assertion must fail for textured lines.
Don't worry about the segfault, that's my own assert macro. Without that
I can't get a backtrace with
I can reproduce this here too. I got a backtrace (see below) and took a
look around s_linetemp.h. There is no INTERP_W for lines so the
assertion must fail for textured lines.
Don't worry about the segfault, that's my own assert macro. Without that
I can't get a backtrace with my gdb+glibc combina
Hi
today after update srcs from cvs trunk (Mesa, drm and xc )
got this error on foobillard 2.9, I send gdb of the bug in debug.txt
file.
thanks
--
Sérgio M. B.
(gdb) run
Starting program: /usr/local/bin/foobillard
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 7262)]
usage:
11 matches
Mail list logo
