public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: SASHA NICOLAS DA ROCHA PINHEIRO <darochapinhe@wisc.edu>
To: Josh Stone <jistone@redhat.com>,
	"elfutils-devel@sourceware.org" <elfutils-devel@sourceware.org>
Subject: Re: Group section
Date: Tue, 21 Mar 2017 20:46:00 -0000	[thread overview]
Message-ID: <BN3PR0601MB13452518E66297F9C53C39A6A63D0@BN3PR0601MB1345.namprd06.prod.outlook.com> (raw)
In-Reply-To: <b9424c7e-a0ed-ee02-b1c1-dda7e1c36632@redhat.com>

That's the problem. It says "no error" once, in another call it says "no reference value", and in another call "no DWARF information".
 
 
De: Josh Stone <jistone@redhat.com>
Enviado: terça-feira, 21 de março de 2017 14:53:12
Para: SASHA NICOLAS DA ROCHA PINHEIRO; elfutils-devel@sourceware.org
Assunto: Re: Group section
    
On 03/21/2017 12:38 PM, SASHA NICOLAS DA ROCHA PINHEIRO wrote:
> 
> Hi Josh
> I am getting error on the following code, and it looks like to be related to group sections.

What is the error?

> As you can see I changed the dwarf_elf_init to dwarf_begin_elf, but passed NULL on the third parameter.
> Do you know how should I actually deal with it? 
> 
>   91 bool DwarfHandle::init_dbg()                                                    
>  92 {                                                                               
>  93     //int status;                                                               
>  94     //Dwarf_Error err;                                                          
>  95     if (init_dwarf_status == dwarf_status_ok) {                                 
>  96         return true;                                                            
>  97     }                                                                           
>  98                                                                                 
>  99     if (init_dwarf_status == dwarf_status_error) {                              
> 100         return false;                                                           
> 101     }                                                                           
> 102                                                                                 
> 103     //status = dwarf_elf_init(file->e_elfp(), DW_DLC_READ,                      
> 104     //                       err_func, &file_data, &file_data, &err);           
> 105                                                                                 
> 106     file_data = dwarf_begin_elf(file->e_elfp(), DWARF_C_READ, NULL);            
> 107     cerr << "Error message:" << dwarf_errmsg(-1) << endl;                       
> 108     if (!file_data) {                                                           
> 109         init_dwarf_status = dwarf_status_error;                                 
> 110         return false;                                                           
> 111     } 
> 

    

  reply	other threads:[~2017-03-21 20:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-21 19:39 SASHA NICOLAS DA ROCHA PINHEIRO
2017-03-21 19:53 ` Josh Stone
2017-03-21 20:46   ` SASHA NICOLAS DA ROCHA PINHEIRO [this message]
2017-03-21 21:24     ` Mark Wielaard

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=BN3PR0601MB13452518E66297F9C53C39A6A63D0@BN3PR0601MB1345.namprd06.prod.outlook.com \
    --to=darochapinhe@wisc.edu \
    --cc=elfutils-devel@sourceware.org \
    --cc=jistone@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).