This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: gsequencer crashes in gdb and in valgrind not
- From: Philippe Waroquiers <philippe dot waroquiers at skynet dot be>
- To: Joël Krähemann <weedlight at gmail dot com>
- Cc: "gdb at sourceware dot org" <gdb at sourceware dot org>
- Date: Fri, 15 May 2015 16:48:06 +0200
- Subject: Re: gsequencer crashes in gdb and in valgrind not
- Authentication-results: sourceware.org; auth=none
- References: <CANr2zYi-Q3Jz5NczW4euAKXad73Mqc8fUoY-VVWZHWDWxrBmpA at mail dot gmail dot com>
On Fri, 2015-05-15 at 13:58 +0000, JoÃl KrÃhemann wrote:
> Hi,what could cause that my program crashes in gdb but with valgrind
> works everything fine?
> Further me don't believe that gdb's stack trace shows me a useful hint:
If you have not done it, you might need to export/set some
gtk env variables such as
G_SLICE=always-malloc
and G_DEBUG=gc-friendly
before launching your gtk application under Valgrind.
That will allow Valgrind to understand better what happens in gtk
memory management.
Otherwise, what is the crash ? a SEGV ?
Philippe