Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Frank Meerkoetter <frank@betaversion.net>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sourceware.org
Subject: Re: multithreaded programs on arm-linux
Date: Thu, 03 Nov 2005 17:51:00 -0000	[thread overview]
Message-ID: <20051103185047.8o634uhdvtsg8kcc@admin.betaversion.net> (raw)
In-Reply-To: <20051103164212.GA2532@nevyn.them.org>

Quoting Daniel Jacobowitz <drow@false.org>:

> On Thu, Nov 03, 2005 at 05:28:09PM +0100, Frank Meerkoetter wrote:
>> thread_db_new_objfile() is called two times.
>> On the first run it prints the library name and
>> than branches on the falg using_thread_db
>> to the label quit.
>> There it returns without executing target_new_objfile_chain (objfile).
>>
>> The second time the same path is followed but without branching into
>> the block protected by the flag dejavu.
>>
>> In neither cases is this line executed:
>>    /* Now attempt to open a connection to the thread library.  */
>>    err = td_ta_new_p (&proc_handle, &thread_agent);
>
> Then what set using_thread_db?

I misinterpreted the indentation level at the first try.
So the paths reported above are a little bit different.
The problem is that we end up in the block below.

static void
thread_db_new_objfile (struct objfile *objfile)
    [...]
    /* Don't attempt to use thread_db on targets which can not run
      (core files).  */
    if (objfile == NULL || !target_has_execution)
     {
       /* All symbols have been discarded.  If the thread_db target is
          active, deactivate it now.  */
       if (using_thread_db)
         {
           gdb_assert (proc_handle.pid == 0);
           unpush_target (&thread_db_ops);
           using_thread_db = 0;
         }
       goto quit;
     }

objfile is NULL, why i couldn't figure out.

Regards,
   Frank



  reply	other threads:[~2005-11-03 17:51 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-01 18:11 frank
2005-11-01 18:22 ` Daniel Jacobowitz
2005-11-02  8:00   ` frank
2005-11-02 12:36     ` Andreas Schwab
2005-11-02 12:46       ` frank
2005-11-02 13:28         ` Andreas Schwab
2005-11-02 13:43           ` Daniel Jacobowitz
2005-11-02 14:33             ` Andreas Schwab
2005-11-02 14:39               ` Daniel Jacobowitz
2005-11-02 15:56                 ` Frank Meerkoetter
2005-11-02 16:49                   ` Daniel Jacobowitz
2005-11-03  8:33                     ` Frank Meerkoetter
2005-11-03 13:56                       ` Daniel Jacobowitz
2005-11-03 15:00                         ` Frank Meerkoetter
2005-11-03 15:07                           ` Daniel Jacobowitz
2005-11-03 15:51                             ` Frank Meerkoetter
2005-11-03 15:59                               ` Daniel Jacobowitz
2005-11-03 16:28                                 ` Frank Meerkoetter
2005-11-03 16:42                                   ` Daniel Jacobowitz
2005-11-03 17:51                                     ` Frank Meerkoetter [this message]
2005-11-03 21:13                                       ` Daniel Jacobowitz
2005-11-04  9:23                                         ` Frank Meerkoetter
2005-11-04 14:25                                           ` Daniel Jacobowitz
2005-11-04 15:39                                             ` Frank Meerkoetter
2005-11-04 15:40                                               ` Daniel Jacobowitz
2005-11-04 15:51                                                 ` Frank Meerkoetter
2005-11-04 16:06                                                 ` Frank Meerkoetter
2005-11-04 16:14                                                   ` Daniel Jacobowitz
2005-11-04 15:41                                               ` Daniel Jacobowitz
2005-11-07  9:26                                                 ` Frank Meerkoetter
2005-11-02 16:52                   ` Andreas Schwab

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=20051103185047.8o634uhdvtsg8kcc@admin.betaversion.net \
    --to=frank@betaversion.net \
    --cc=drow@false.org \
    --cc=gdb@sourceware.org \
    /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