From: SZOKOVACS Robert <szo@ies.hu>
To: <gdb-patches@sources.redhat.com>
Subject: meaningful error message in gdbserver
Date: Wed, 31 Aug 2005 19:04:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.33.0508311929060.17751-100000@server.ies-hungary.intra> (raw)
Hi,
I had a long day fighting with remote debugging, until I found out that my
libpthread and libthread_db versions didn't match. So I created the patch
below that makes gdbserver more verbose when failing, maybe it can save
some time for somebody in the future.
br
Szo
==========================================================================
diff -ruw gdb-6.3.50.20050831-orig/gdb/gdbserver/thread-db.c gdb-6.3.50.20050831/gdb/gdbserver/thread-db.c
--- gdb-6.3.50.20050831-orig/gdb/gdbserver/thread-db.c 2005-08-31 18:12:56.000000000 +0200
+++ gdb-6.3.50.20050831/gdb/gdbserver/thread-db.c 2005-08-31 18:27:18.000000000 +0200
@@ -351,6 +351,10 @@
/* No thread library was detected. */
return 0;
+ case TD_VERSION:
+ warning ("error initializing thread_db library:\nVersion of libpthread and libthread_db mismatch.");
+ return 0;
+
case TD_OK:
/* The thread library was detected. */
next reply other threads:[~2005-08-31 17:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-31 19:04 SZOKOVACS Robert [this message]
2005-09-17 23:12 ` Daniel Jacobowitz
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=Pine.LNX.4.33.0508311929060.17751-100000@server.ies-hungary.intra \
--to=szo@ies.hu \
--cc=gdb-patches@sources.redhat.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