public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Nurdin Premji <npremji@redhat.com>
To: Roland McGrath <roland@redhat.com>, frysk <frysk@sourceware.org>
Subject: Elfutils module reporting
Date: Mon, 16 Jul 2007 20:05:00 -0000	[thread overview]
Message-ID: <469BCF76.50103@redhat.com> (raw)

Roland, I'm trying to refresh dwfl objects in terms of the dwfl_modules. 
To optimize code and not create a new dwfl object every time a task changes.
As a first pass I was trying to remove all old modules and re-report new 
modules just by using dwfl_report_begin and dwfl_report_end. The 
libdwfl.h comments lead me to believe this is all that is necessary to 
remove all old modules and report only new modules. I plan to switch to 
dwfl_report_begin_add later on and only report modules that have changed.

I got an assertion failure at the dwfl_report_end stage
 /home/yyz/npremji/mainworkspace/frysk/frysk-imports/elfutils/libdwfl/dwfl_module.c:249: 
dwfl_report_end: Assertion `i == dwfl->nmodules' failed.

Looking at the dwfl_module.c file I see that dwfl_report_begin calls 
dwfl_report_begin_add, which clears all the modules. I thought that this 
function was supposed to preserver all the old modules?

Also how would I go about removing single modules in an updating 
scenario? i.e. is there a dwfl_report_remove_module function to link 
with dwfl_report_begin_add?

Thank you,
Nurdin.

             reply	other threads:[~2007-07-16 20:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-16 20:05 Nurdin Premji [this message]
2007-07-16 20:41 ` Roland McGrath
2007-07-16 22:00   ` Nurdin Premji
2007-07-16 22:25     ` Roland McGrath

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=469BCF76.50103@redhat.com \
    --to=npremji@redhat.com \
    --cc=frysk@sourceware.org \
    --cc=roland@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).