Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@vmware.com>
To: "D. Hugh Redelmeier" <hugh@mimosa.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Cannot get thread event message: debugger service failed
Date: Mon, 01 Dec 2008 22:27:00 -0000	[thread overview]
Message-ID: <49346409.7010508@vmware.com> (raw)
In-Reply-To: <alpine.LRH.2.00.0811250250530.9586@redclaw.mimosa.com>

D. Hugh Redelmeier wrote:
> 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

I have only a few random guesses.

1) Can you try building gdb from sources on your host machine?
Could conceivably be some sort of header file issue.

2) We can see where the error message comes from: void check_event
in linux-thread-db.c.  It's not very informative, it just tells us
that the call to td_ta_event_getmsg_p failed.  No reason for that
suggests itself, other than
   1) maybe mis-matched header files
   2) maybe privilege issues?  Does firefox run as priveleged?
I'm guessing that at least parts of it must, otherwise you would
not be seeing it taking over and hanging up your X server.

If its a privilege issue, can you try running gdb as root?

 > Sometimes the screen locks up until the "continue".  So I need to run
 > GDB somewhere other than the X desktop.

Yeah, this suggests that firefox is grabbing some locks or resources
from the X server, which may suggest that it's running privileged.
You're already running gdb from a separate pseudo-console, might as
well try running it as root as well...


  reply	other threads:[~2008-12-01 22:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-25  8:10 D. Hugh Redelmeier
2008-12-01 22:27 ` Michael Snyder [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-10-25  7:05 Gdb Russell Shaw
2006-10-26 12:41 ` Cannot get thread event message: debugger service failed Christophe Benoit
2006-10-26 12:45   ` Daniel Jacobowitz
2006-10-26 13:31     ` Christophe Benoit

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49346409.7010508@vmware.com \
    --to=msnyder@vmware.com \
    --cc=gdb@sourceware.org \
    --cc=hugh@mimosa.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox