Re: [Tuxpaint-devel] Kaleidoscope crash

[Caroline F. <car...@go...>]

On 01/12/2007, Albert Cahalan <aca...@gm...> wrote:
> If using gdb, then use Electric Fence at the same time.
> Without that, the crash is likely to be in unrelated code.
> The bad code overflows a buffer, but this doesn't cause
> an immediate crash. Later, good code calls malloc()
> and gets a crash because malloc() walks a corrupt list.
> Electric Fence puts unmapped memory after each allocation,
> causing crashes to be immediate and making gdb useful.
>
> You can:
>
> a. link with -lefence
> b. set LD_PRELOAD to the name of the libefence *.so
> c. use the "ef" program, which sets LD_PRELOAD for you
>
> See "man efence" for extra info; setting the alignment
> to 0 would be a good idea.
>
> There are many things this won't spot though. Valgrind
> is probably the better tool.
>
I was using the standard Ubuntu program crash rules. We ask them for a
backtrace https://wiki.ubuntu.com/Backtrace using gbd and then using
Valgrind https://wiki.ubuntu.com/Valgrind

My concern is that I can't get a debug version of tuxpaint.  I'm
guessing I'd need to hack on the makefiles.