Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Carlo Wood <carlo@alinoe.com>
Cc: liams@redhat.com, gdb@sources.redhat.com
Subject: Re: gdb bugs showing while working on libcwd
Date: Sun, 26 May 2002 23:03:00 -0000	[thread overview]
Message-ID: <20020527060329.GA5078@branoic.them.org> (raw)
In-Reply-To: <20020527034255.A25457@alinoe.com>

On Mon, May 27, 2002 at 03:42:55AM +0200, Carlo Wood wrote:
> (gdb) p __libcwd_tsd
> $1 = (TSD_st &) @0x8075968: {internal = 1, library_call = 0, inside_malloc_or_free = 0, memblk_map = 0x0, marker = 0,
>   recursive_fatal = false, recursive_assert = true, cancel_explicitely_deferred = 0, cancel_explicitely_disabled = 0,
>   inside_critical_area = 0, cleanup_handler_installed = 0, internal_debugging_code = 1, tid = 1026, do_off_array = {0, 0, 0, 0, 0, 0, 0, 0},

>   do_array = {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}, off_cnt_array = {0 <repeats 256 times>}, static S_exit_key = Internal: global symbol `_ZN5libcw5debug9_private_6TSD_st10S_exit_keyE'


**
>found in threading.cc psymtab but not in symtab.
**

> _ZN5libcw5debug9_private_6TSD_st10S_exit_keyE may be an inlined function, or may be a template function
> (if a template, try specifying an instantiation: _ZN5libcw5debug9_private_6TSD_st10S_exit_keyE<type>).
> (gdb)
> 
> _ZN5libcw5debug9_private_6TSD_st10S_exit_keyE
> 
> is
> 
**
> libcw::debug::_private_::TSD_st::S_exit_key
**

> A static member of struct TSD_st (in namespace
> libcw::debug::_private_) of type pthread_key_t.
> 
> Hence, it is NOT a inlined function (or a function at all),
> nor is it a template.  It is also very surely instantiated ;).
> 
> Don't tell me this is related to namespaces too :/

[** Emphasis ** mine **]

Of course it is; it's in a namespace.  Really, I don't expect any of
what you're doing to work right now.  My first stab at fixing it was a
complete disaster, too...

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-05-27  6:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020522115242.C28512@redhat.com>
     [not found] ` <20020523153816.A4454@alinoe.com>
     [not found]   ` <20020523094527.B25730@redhat.com>
2002-05-23 17:35     ` Carlo Wood
2002-05-23 18:58       ` Daniel Jacobowitz
2002-05-24  8:41   ` Huge problems with debugging threaded C++ programs Liam Stewart
2002-05-24  9:42     ` gdb bugs showing while working on libcwd Carlo Wood
2002-05-24 18:33       ` Carlo Wood
2002-05-24 18:41         ` Daniel Jacobowitz
2002-05-26 18:43           ` Carlo Wood
2002-05-26 23:03             ` Daniel Jacobowitz [this message]
2002-05-27  5:42               ` Carlo Wood
2002-05-27 11:05                 ` Daniel Jacobowitz
2002-05-27 17:01                   ` Carlo Wood
2002-05-28  1:17                     ` Daniel Jacobowitz
2002-05-28  5:50                       ` Carlo Wood
2002-05-28 10:37                         ` Daniel Jacobowitz
2002-05-28 15:54                           ` Carlo Wood

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=20020527060329.GA5078@branoic.them.org \
    --to=drow@mvista.com \
    --cc=carlo@alinoe.com \
    --cc=gdb@sources.redhat.com \
    --cc=liams@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