From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24171 invoked by alias); 17 May 2012 20:22:52 -0000 Received: (qmail 24161 invoked by uid 22791); 17 May 2012 20:22:50 -0000 X-SWARE-Spam-Status: No, hits=-6.5 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,RCVD_IN_DNSWL_HI,RCVD_IN_HOSTKARMA_W,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 17 May 2012 20:22:35 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q4HKMXO5014784 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 17 May 2012 16:22:33 -0400 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id q4HKMVGg007077 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 17 May 2012 16:22:32 -0400 From: Tom Tromey To: "erupter\@libero.it" Cc: gdb@sourceware.org Subject: Re: Gdb crashing or not attaching in Netbeans References: <29722524.2084501337265496433.JavaMail.defaultUser@defaultHost> Date: Thu, 17 May 2012 20:22:00 -0000 In-Reply-To: <29722524.2084501337265496433.JavaMail.defaultUser@defaultHost> (erupter@libero.it's message of "Thu, 17 May 2012 16:38:16 +0200 (CEST)") Message-ID: <87vcjuk16g.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.95 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain 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 X-SW-Source: 2012-05/txt/msg00079.txt.bz2 >>>>> "Claudio" == erupter@libero it writes: Claudio> Now Netbeans doesn't provide any info at all to help me debug Claudio> this, so I'm asking here: how can I gather information on this Claudio> kind of malfunction? One way is to try to reproduce the problem outside of Netbeans. Or, if gdb is crashing, you could enable core dumps. Or, you can ask the Netbeans people for advice. Often GUIs using gdb have debugging modes where they display the MI streams. Tom