From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24008 invoked by alias); 25 Nov 2008 08:10:33 -0000 Received: (qmail 23981 invoked by uid 22791); 25 Nov 2008 08:10:32 -0000 X-Spam-Check-By: sourceware.org Received: from gw-d.mimosa.com (HELO gw-d.mimosa.com) (209.161.207.149) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 25 Nov 2008 08:09:42 +0000 Received: from redclaw.mimosa.com (redclaw.mimosa.com [192.139.70.88]) by gw-d.mimosa.com (8.12.8/8.12.8) with ESMTP id mAP89WRR018630 for ; Tue, 25 Nov 2008 03:09:32 -0500 Date: Tue, 25 Nov 2008 08:10:00 -0000 From: "D. Hugh Redelmeier" Reply-To: "D. Hugh Redelmeier" To: gdb@sourceware.org Subject: Cannot get thread event message: debugger service failed Message-ID: User-Agent: Alpine 2.00 (LRH 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-IsSubscribed: yes 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: 2008-11/txt/msg00151.txt.bz2 I'm trying to debug Firefox on Linux. I'm using GDB. Execution of Firefox is frequently interrupted with this message: [New Thread 0x44125950 (LWP 30469)] Cannot get thread event message: debugger service failed At this point, I enter a "continue" GDB command and execution proceeds. Sometimes the screen locks up until the "continue". So I need to run GDB somewhere other than the X desktop. What is the best way to avoid this problem and get on with debugging Firefox? (I admit: a quixotic quest.) Google finds this for me: http://sourceware.org/ml/gdb/2006-10/msg00259.html but I don't see a resolution. Some details: - I get this message on 64-bit Fedora 9 (on a dual-core machine) and on 64-bit Ubuntu 8.04 (on a quad core machine) - GDB on Fedora 9: gdb-6.8-23.fc9.x86_64 - GDB on Ubuntu 8.04: 6.8-1ubuntu3 - I run Firefox this way: Firefox --sync or: Firefox --sync -no-remote - I run gdb later, giving it the executable file and the PID - I tell gdb to ignore sigpipe signals: handle SIGPIPE nostop - I then let GDB continue Firefox - after a small amount of browsing, the dreaded message shows up