Dwarves debugging tools
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: "Diego 'Flameeyes' Pettenò"
	<flameeyes-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: dwarves-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Errors during a pfunct scan for amarokcollectionscanner and inkscape
Date: Mon, 16 Jun 2008 15:14:18 -0300	[thread overview]
Message-ID: <20080616181418.GA4471@ghostprotocols.net> (raw)
In-Reply-To: <20080615180233.GD4597-f8uhVLnGfZaxAyOMLChx1axOck334EZe@public.gmane.org>

Em Sun, Jun 15, 2008 at 03:02:33PM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Sun, Jun 15, 2008 at 02:13:27PM -0300, Arnaldo Carvalho de Melo escreveu:
> > Em Sat, Jun 14, 2008 at 11:43:44AM +0200, Diego 'Flameeyes' Pettenò escreveu:
> > > 
> > > Hi :)
> > > 
> > > On http://www.flameeyes.eu/tmp/dwarves-again.tbz2 you can find the
> > > executables amarokcollectionscanner and inkscape from my workstation
> > > (Gentoo Linux AMD64), they report these errors when scaning them with
> > > pfunct:
> > > 
> > > flame@enterprise ~ % pfunct /usr/bin/amarokcollectionscanner
> > > dwarf_expr: unhandled 0x12 DW_OP_ operation
> > > dwarf_expr: unhandled 0x12 DW_OP_ operation
> > > 
> > > as for inkscape:
> > > 
> > > die__create_new_subroutine_type: DW_TAG_typedef @ <0x6efd> not handled!
> 
> Really strange case:
> 
>  <1><6d90>: Abbrev Number: 5 (DW_TAG_subroutine_type)
>     <6d91>   DW_AT_sibling     : <0x6dba>       
>  <2><6d95>: Abbrev Number: 6 (DW_TAG_formal_parameter)
>     <6d96>   DW_AT_type        : <0x50> 
>  <2><6d9a>: Abbrev Number: 6 (DW_TAG_formal_parameter)
>     <6d9b>   DW_AT_type        : <0x6d9f>       
>  <2><6d9f>: Abbrev Number: 11 (DW_TAG_typedef)
>     <6da0>   DW_AT_name        : (indirect string, offset: 0x1a977): CleanupFunc        
>     <6da4>   DW_AT_decl_file   : 18     
>     <6da5>   DW_AT_decl_line   : 46     
>     <6da6>   DW_AT_type        : <0x6a71>       
>  <2><6daa>: Abbrev Number: 6 (DW_TAG_formal_parameter)
>     <6dab>   DW_AT_type        : <0x50> 
>  <2><6daf>: Abbrev Number: 6 (DW_TAG_formal_parameter)
>     <6db0>   DW_AT_type        : <0x6dba>       
>  <2><6db4>: Abbrev Number: 6 (DW_TAG_formal_parameter)
>     <6db5>   DW_AT_type        : <0x66c6>
> 
> This maps to something like this:
> 
> typedef void (*CleanupFunc)(void *mem, void *data);
> 
> struct Ops {
>     void (*do_init)();
>     void *(*malloc)(std::size_t size);
>     void *(*malloc_atomic)(std::size_t size);
>     void *(*malloc_uncollectable)(std::size_t size);
>     void *(*malloc_atomic_uncollectable)(std::size_t size);
>     void *(*base)(void *ptr);
>     void (*register_finalizer_ignore_self)(void *base,
>                                            CleanupFunc func, void *data,
>                                            CleanupFunc *old_func,
>                                            void **old_data);
> 
> Meaning that the typedef was not encoded right away, but postponed till
> just after its first use, i.e. in the parameter list of
> register_finalizer_ignore_self, as if it was local to this function.
> Later on it is again referenced, so its not local, as expected, I'll fix
> it, have just to check where to insert this typedef.

Fixed, I'm now adding the DW_TAG_typedef entries to the compile unit
where the DW_TAG_subroutine_type is defined.

This:

dwarf_expr: unhandled 0x12 DW_OP_ operation

is probably related to pure virtual base classes, this will require a
bit more work but its something its in my TODO list for quite a while,
so I may well implement support for location expressions.

- Arnaldo
--
To unsubscribe from this list: send the line "unsubscribe dwarves" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2008-06-16 18:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-14  9:43 Errors during a pfunct scan for amarokcollectionscanner and inkscape Diego 'Flameeyes' Pettenò
     [not found] ` <m2lk18qrlb.fsf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2008-06-15 17:13   ` Arnaldo Carvalho de Melo
     [not found]     ` <20080615171327.GC4597-f8uhVLnGfZaxAyOMLChx1axOck334EZe@public.gmane.org>
2008-06-15 18:02       ` Arnaldo Carvalho de Melo
     [not found]         ` <20080615180233.GD4597-f8uhVLnGfZaxAyOMLChx1axOck334EZe@public.gmane.org>
2008-06-16 18:14           ` Arnaldo Carvalho de Melo [this message]

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=20080616181418.GA4471@ghostprotocols.net \
    --to=acme-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=dwarves-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=flameeyes-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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