From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24177 invoked by alias); 12 May 2014 03:25:00 -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 24162 invoked by uid 89); 12 May 2014 03:24:58 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-yh0-f45.google.com Received: from mail-yh0-f45.google.com (HELO mail-yh0-f45.google.com) (209.85.213.45) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Mon, 12 May 2014 03:24:57 +0000 Received: by mail-yh0-f45.google.com with SMTP id b6so5791549yha.4 for ; Sun, 11 May 2014 20:24:55 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.236.157.167 with SMTP id o27mr38273046yhk.127.1399865095208; Sun, 11 May 2014 20:24:55 -0700 (PDT) Received: by 10.170.222.7 with HTTP; Sun, 11 May 2014 20:24:55 -0700 (PDT) In-Reply-To: <83ha54zrry.fsf@gnu.org> References: <83ha54zrry.fsf@gnu.org> Date: Mon, 12 May 2014 03:25:00 -0000 Message-ID: Subject: Re: [PATCH v2 00/36] Guile extension language for GDB From: Doug Evans To: Eli Zaretskii Cc: Tillmann Karras , "gdb-patches@sourceware.org" , =?UTF-8?Q?Ludovic_Court=C3=A8s?= Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes X-SW-Source: 2014-05/txt/msg00130.txt.bz2 [+ ludovic] On Sun, May 4, 2014 at 11:03 PM, Eli Zaretskii wrote: >> Date: Sun, 04 May 2014 21:59:08 +0200 >> From: Tillmann Karras >> Cc: gdb-patches@sourceware.org >> >> 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. > > My crystal ball says that Ctrl-C causes Guile to start its signal > delivery thread, which is the reason for the "New Thread" message you > see. > >> > 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?) > > What bug is that in libgc, and what are its symptoms? A google search for libgc 7.4 GC_MARKERS found this: https://lists.gnu.org/archive/html/guile-commits/2014-04/msg00051.html