From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2930 invoked by alias); 4 May 2014 19:59:15 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 2919 invoked by uid 89); 4 May 2014 19:59:13 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.2 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2 X-HELO: mail.wh-stuttgart.net Received: from mail.wh-stuttgart.net (HELO mail.wh-stuttgart.net) (141.70.126.65) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Sun, 04 May 2014 19:59:11 +0000 Received: from localhost (localhost [127.0.0.1]) by mail.wh-stuttgart.net (Postfix) with ESMTP id BAC1F1813BF; Sun, 4 May 2014 21:59:08 +0200 (CEST) Received: from mail.wh-stuttgart.net ([127.0.0.1]) by localhost (mail.selfnet.de [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id cNwBt2RO8-Wa; Sun, 4 May 2014 21:59:08 +0200 (CEST) Received: from roundcube.wh-stuttgart.net (localhost [127.0.0.1]) by mail.wh-stuttgart.net (Postfix) with ESMTPSA; Sun, 4 May 2014 21:59:08 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Sun, 04 May 2014 19:59:00 -0000 From: Tillmann Karras To: Doug Evans Cc: gdb-patches@sourceware.org Subject: Re: [PATCH v2 00/36] Guile extension language for GDB In-Reply-To: References: Message-ID: X-Sender: tillmann@selfnet.de User-Agent: Roundcube Webmail/0.9.4 X-SW-Source: 2014-05/txt/msg00030.txt.bz2 On 2014-04-28 00:15, Doug Evans wrote: > If you're running gdb under gdb, and the child gdb is hanging, > can you type Ctrl-C when it hangs, and then obtain a backtrace of the > child gdb? Pressing Ctrl-C just prints "[New Thread 0x7ffff4b6f700 (LWP 14601)]" but I don't get any prompt. > It's been suggested to give the following a try. > Does that fix things for you? > > bash$ export GC_MARKERS=1 > > before starting gdb > It's a workaround for a libgc 7.4.0 bug. > I verified my arch-linux has libgc 7.4.0, but I may have just gotten > lucky. Yes, "gdb -ex 'set environment GC_MARKERS 1' -ex r gdb" makes it work for me. (Maybe your test VM had only one core?)