From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 106040 invoked by alias); 15 May 2015 14:47:40 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 106025 invoked by uid 89); 15 May 2015 14:47:40 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mailrelay105.isp.belgacom.be Received: from mailrelay105.isp.belgacom.be (HELO mailrelay105.isp.belgacom.be) (195.238.20.132) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 15 May 2015 14:47:38 +0000 X-Belgacom-Dynamic: yes X-Cloudmark-SP-Filtered: true X-Cloudmark-SP-Result: v=1.1 cv=KjSUzZxnmGSQ+6+vr4Kd0OSSUs/Ia9ciENKrYVIfwLU= c=1 sm=2 a=IkcTkHD0fZMA:10 a=Wms-sluXPFqst7xgydQA:9 a=QEXdDO2ut3YA:10 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2C+AQCIBlZV/7LMgG0NT4dfyBGBDgKCBQEBAQEBAYUuAQEEIw8BRhALGAICJgICVwaIRLFhcKREAQEBAQEFAQEBAQEdgSGKGYUFB4JogUUBBJ57kgCDWIQdgzMBAQE Received: from 178.204-128-109.adsl-dyn.isp.belgacom.be (HELO [192.168.1.11]) ([109.128.204.178]) by relay.skynet.be with ESMTP; 15 May 2015 16:47:36 +0200 Subject: Re: gsequencer crashes in gdb and in valgrind not From: Philippe Waroquiers To: =?ISO-8859-1?Q?Jo=EBl_Kr=E4hemann?= Cc: "gdb@sourceware.org" In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Date: Fri, 15 May 2015 14:47:00 -0000 Message-ID: <1431701286.18605.41.camel@soleil> Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-IsSubscribed: yes X-SW-Source: 2015-05/txt/msg00016.txt.bz2 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