Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Hui Zhu <teawater@gmail.com>
To: Paul Pluzhnikov <ppluzhnikov@google.com>
Cc: tromey@redhat.com, Thiago Jung Bauermann <bauerman@br.ibm.com>,
	 	gdb-patches ml <gdb-patches@sourceware.org>,
	Eli Zaretskii <eliz@gnu.org>
Subject: Re: [patch][rfc] Allow GDB to search for the right libthread_db.so.1
Date: Thu, 23 Apr 2009 11:32:00 -0000	[thread overview]
Message-ID: <daef60380904230432l7f49d44dw17437e208b35cb9f@mail.gmail.com> (raw)
In-Reply-To: <daef60380904230105u20843291pe8ee9f98e5ed1d76@mail.gmail.com>

In function thread_db_load, I suggest try_thread_db_load with
libthread_db_search_path first.
Cause I think if user set a directory, he must want it be loaded.


Thanks,
Hui

On Thu, Apr 23, 2009 at 16:05, Hui Zhu <teawater@gmail.com> wrote:
> On Thu, Apr 23, 2009 at 15:01, Paul Pluzhnikov <ppluzhnikov@google.com> wrote:
>> On Wed, Apr 22, 2009 at 11:21 PM, Hui Zhu <teawater@gmail.com> wrote:
>>
>>> About your patch, I think let user choice load which libthread_db is
>>> very cool idea.
>>> Why not let they set which file they want to load directly?
>>>
>>> For example:
>>> set libthread-db /xxx_dir/libxxx
>>
>> As I stated at the start of this thread, we have a mixture of
>> executables: some are linked statically, some dynamically, and
>> against several (incompatible WRT libthread_db) glibc versions.
>>
>> I'd like GDB to work "automagically" for all such executables,
>> without the end user having to understand and specify exactly
>> which libthread_db must be loaded for each one [1].
>>
>> The patch allows me to achieve that (all I need to do is provide
>> appropriate local definition of LIBTHREAD_DB_SEARCH_PATH).
>>
>> [1] Understanding this requires the user to understand how
>> GDB uses libthread_db and the relationship between libpthread and
>> libthread_db. Also, the mapping is complicated by the fact that
>> 64-bit GDB is sometimes used to debug 32-bit inferiors.
>>
>
> I read your patch again, And I think let user set file name is not
> conflict with your patch.
> In thread_db_load_search:
> +  while (*search_path)
> +    {
> +      const char *end = strchr (search_path, ':');
> +      if (end)
> +       {
> +         size_t len = end - search_path;
> +          if (len + 1 + strlen (LIBTHREAD_DB_SO) + 1 > sizeof (path))
> +            {
> +              char *cp = xmalloc (len + 1);
> +              memcpy (cp, search_path, len);
> +              cp[len] = '\0';
> +              warning (_("libthread_db_search_path component too long,"
> +                         " ignored: %s."), cp);
> +              xfree (cp);
> +              search_path += len + 1;
> +              continue;
> +            }
> +         memcpy (path, search_path, len);
> +         path[len] = '\0';
> +         search_path += len + 1;
> +       }
> +      else
> +       {
> +          size_t len = strlen (search_path);
> +
> +          if (len + 1 + strlen (LIBTHREAD_DB_SO) + 1 > sizeof (path))
> +            {
> +              warning (_("libthread_db_search_path component too long,"
> +                         " ignored: %s."), search_path);
> +              break;
> +            }
> +         memcpy (path, search_path, len + 1);
> +         search_path += len;
> +       }
>
> When you get a path, you can check if this is a directory.
>
> If this is a directory, do following job.
>
> +      strcat (path, "/");
> +      strcat (path, LIBTHREAD_DB_SO);
> +      if (try_thread_db_load (path))
> +       {
> +         rc = 1;
> +         break;
> +       }
>
> If this is a normal file, try_thread_db_load (path) without strcat
> LIBTHREAD_DB_SO.
>
> What do you think about it?
>
>
> And in thread_db_load:
> +  msym = lookup_minimal_symbol ("nptl_version", NULL, NULL);
> +  if (!msym)
> +    msym = lookup_minimal_symbol ("__linuxthreads_version", NULL, NULL);
> +
> +  /* Some really old libpthread versions do not have either of the above.  */
> +  if (!msym)
> +    msym = lookup_minimal_symbol ("__pthread_threads_events", NULL, NULL);
> +
> +  if (!msym)
> +    /* No threads yet */
> +    return 0;
>
> You really don't want gdb try it with libthread_db?
> If in the future, this code doesn't cover everything.  And I think let
> gdb try will not affect anything.  :)
>
> Thanks,
> Hui
>


  reply	other threads:[~2009-04-23 11:32 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-06 20:39 Paul Pluzhnikov
2009-04-08 21:23 ` Thiago Jung Bauermann
2009-04-10 19:06   ` Paul Pluzhnikov
2009-04-16 17:56     ` Tom Tromey
2009-04-16 18:22       ` Eli Zaretskii
2009-04-17 19:13       ` Paul Pluzhnikov
2009-04-18 17:01         ` Eli Zaretskii
2009-04-19 14:59         ` Thiago Jung Bauermann
2009-04-19 18:03           ` Paul Pluzhnikov
2009-04-20 13:18         ` Daniel Jacobowitz
2009-04-20 16:47           ` Paul Pluzhnikov
2009-04-20 17:02             ` Daniel Jacobowitz
2009-04-20 17:20               ` Paul Pluzhnikov
2009-04-20 18:04                 ` Daniel Jacobowitz
2009-04-20 19:09                   ` Paul Pluzhnikov
2009-04-22 17:25                     ` Daniel Jacobowitz
2009-04-23  1:10                       ` Paul Pluzhnikov
2009-04-23  1:34                         ` Tom Tromey
2009-04-23  6:28                           ` Hui Zhu
2009-04-23  6:21                         ` Hui Zhu
2009-04-23  7:01                           ` Paul Pluzhnikov
2009-04-23  8:06                             ` Hui Zhu
2009-04-23 11:32                               ` Hui Zhu [this message]
2009-04-29 20:30                                 ` Paul Pluzhnikov
2009-04-30  5:38                                   ` Hui Zhu
2009-04-30 18:56                                   ` Joel Brobecker
2009-04-30 19:11                                     ` Paul Pluzhnikov
2009-04-30 22:12                                       ` Doug Evans
2009-04-30 23:18                                       ` Paul Pluzhnikov
2009-05-01  0:20                                         ` Paul Pluzhnikov
2009-05-11 13:13                                           ` Pedro Alves
2009-05-11 18:09                                             ` Paul Pluzhnikov
2009-05-11 21:09                                               ` Pedro Alves
2009-05-12  7:16                                               ` Hui Zhu
2009-05-12 16:42                                                 ` Paul Pluzhnikov
2009-05-13  2:56                                                   ` Hui Zhu
2009-05-13  3:29                                                     ` Paul Pluzhnikov
2009-05-13  4:39                                                       ` Hui Zhu
2009-05-15 14:37                                               ` Daniel Jacobowitz
2009-05-15 16:56                                                 ` Paul Pluzhnikov
2009-05-01  7:21                                         ` Eli Zaretskii
2009-05-01 15:49                                           ` Paul Pluzhnikov
2009-05-01 16:49                                             ` Daniel Jacobowitz
2009-05-01 17:02                                               ` Paul Pluzhnikov
2009-05-01 17:11                                                 ` Daniel Jacobowitz
2009-05-01 17:17                                                 ` Pedro Alves
2009-05-01 18:53                                                   ` Doug Evans
2009-05-04  0:07                                     ` Hui Zhu
2009-05-04  3:31                                       ` Paul Pluzhnikov
2009-05-05  2:54                                         ` Hui Zhu
2009-05-05  3:38                                           ` Joel Brobecker
2009-05-05 11:42                                             ` Hui Zhu
2009-05-11 11:34                                               ` Pedro Alves
2009-05-11 12:24                                                 ` Joel Brobecker
2009-04-20 17:37             ` Paul Pluzhnikov
2009-04-20 18:46               ` Eli Zaretskii
2015-08-25 18:01 ` Jan Kratochvil
2015-08-25 18:14   ` Paul Pluzhnikov
2015-08-25 18:22     ` Jan Kratochvil

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=daef60380904230432l7f49d44dw17437e208b35cb9f@mail.gmail.com \
    --to=teawater@gmail.com \
    --cc=bauerman@br.ibm.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=ppluzhnikov@google.com \
    --cc=tromey@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