public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
To: "Joël Krähemann" <weedlight@gmail.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: gsequencer crashes in gdb and in valgrind not
Date: Fri, 15 May 2015 14:47:00 -0000	[thread overview]
Message-ID: <1431701286.18605.41.camel@soleil> (raw)
In-Reply-To: <CANr2zYi-Q3Jz5NczW4euAKXad73Mqc8fUoY-VVWZHWDWxrBmpA@mail.gmail.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



      parent reply	other threads:[~2015-05-15 14:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-15 13:58 Joël Krähemann
2015-05-15 14:22 ` Joël Krähemann
2015-05-15 14:47 ` Philippe Waroquiers [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1431701286.18605.41.camel@soleil \
    --to=philippe.waroquiers@skynet.be \
    --cc=gdb@sourceware.org \
    --cc=weedlight@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).