I happened to stumble upon backends/sparc_retval.c which still has an
old license header. It was added in commit c373d8 by Roland after the
project as a whole had switched to the GPL. I assume that was an
oversight since it is the only file not marked with the same license
header as all other files.
OK, to push this fixup?
I noticed something in __libdw_visit_scopes that seems weird to me.
When a DW_TAG_imported_unit is encountered, the child.die is overwritten
with the importee. This means:
1. The previsit is called on the importer.
2. The recursion is called on the importee.
3. The postvisit is called on the importee.
4. The next sibling is read from the importee.
It's inconsistent at least, which makes me wonder if it might do the
wrong thing, especially in the sibling walk. If the importer had any
siblings following, they will not be seen.
I haven't seen any actual use of imported_unit, so I don't know if this
has any real impact, but I thought I should raise the flag.
I was getting some crashes because the struct Dwarf_CFI ebl field
sometimes contained garbage. This patch explicitly clears the field in
dwarf_getcfi after the structure is allocated through
libdw_typed_alloc(). Other locations where a struct Dwarf_CFI is created
aren't a problem since they allocate through calloc() which guarantees
the memory is cleared.
OK to push?
> msgid: '%' is only meaningful with the 'x' option
That was indeed a typo in our format string (meant to be %c).
Thanks for catching that! I've fixed it in the latest git tree
on our fedorahosted repo.
It would be nice if the canonical po/Makefile's "make check"
would do something that would catch those msgfmt errors in the
package build before it gets to the translators.
I stumbled upon one more case of an apparently wrong translation:
po/it.po in elfutils project in fact localizes strings from some sort of
Fedora/Python integration package. (For members of fedora-trans-it(a)r.c,
the previous case was Spanish.)
So it seems to be common mishap that someone somehow commits to elfutils
translation of other project. I don't know how this thing works at all,
and so don't have any theories on why, nor any ideas on how to prevent it.
I was looking at commits to master branch of elfutils. Just below HEAD,
we have two commits related to Spanish translation, both of which are
b70263b0a78ac5d98b382932c8506a2f58c11963 simply removes some
translations. This may actually be legitimate, perhaps they were wrong,
but it does look suspicious. I don't speak any Spanish at all, so can't
check it myself.
5658eef4d3c51333d23eb8d1adfbbd2b0e80a19f replaces translations of
elfutils strings with translations of:
So you see a lot of chunks like this one:
-msgid "invalid fmag field in archive header"
+msgid "log entry"
+msgstr "entrada de registro"
I started this conversation with Roland on #systemtap. At first I was
asking about ways that I might cache some of the DIE traversals, but I
think the issues we were talking about are actually orthogonal to caching.
The point we got to is that the planned dwarf compression techniques
will graft common DIE subtrees together, so there may be multiple paths
from a CUDIE to some other DIE. When you call dwarf_getscopes[_die],
the traversal stops at the first complete chain it finds. The
discussion then is how to decide whether a particular graft would make
an incompatible change in the resolved scopes.
For example, suppose we have A::foo() and B::foo(), and some subtrees in
foo are identical, so we want to omit the B::foo subtree and just link
it to A::foo. Is this consolidation ok? The answer probably depends on
what the dwarf is used for.
Currently in systemtap, we use dwarf_getscopes to get the lexical
hierarchy for resolving variables, and dwarf_getscopes_die to get the
physical hierarchy for resolving the frame base. As long as A:: and B::
really have the same variable scopes, I think it should be fine to merge
I want to add systemtap support for matching and showing the
fully-scoped name of a function. It seems the way to do this is to call
getscopes_die on the specification, and walk up the result to get
namespace::class::etc. I think the compression won't have combined
anything in this path, since they'll have different decl_file/line, etc.
Now that I've written this out, I'm actually not seeing anything that
compression is likely to break for us. Either I'm forgetting something
else that stap does or could do, or I was worrying for nothing.
Or perhaps Roland has some really bizarre cases where things might be
merged? He said that some of it depends on what assumptions we're
making as users, so maybe I need my assumptions pointed out to me... :)
Employs them in the service of religion. Every faculty of body and soul,
when considered as a part of "the purchased possession" of the Saviour,
assumes a new character. How powerfully does the apostle on this ground
urge a plea for holy activity and watchfulness! "What! know ye not that
your body is the temple of the Holy Ghost which is in you, which ye have
of God, and ye are not your own? For ye are bought with a price;
therefore glorify God in your body, and in your spirit, which are
God's." The Christian may derive much profit and enjoyment from the use
of the memory as it concerns those transactions in which he once bore a
part. In his endeavours to recall past conversations and intercourse
with deceased friends, in particular, the powers of remembrance greatly
improve by exercise. One revived idea produces another, till the mind is
most agreeably and usefully occupied with lively and holy imaginations.
"Lulled in the countless chambers of the brain, Our thoughts are linked
by many a hidden chain. Awake but one, and lo! what myriads rise! Each
stamps its image as the other flies. Each, as the varied avenues of
sense Delight or sorrow to the soul dispense, Brightens or fades; yet
all, with sacred art, Control the latent fibres of the heart." May it
please God to bless, both to the reader and the writer, this feeble
attempt to recollect some of the communications which I once enjoyed in
my visits to the Dairyman's dwelling. Very soon after the receipt of the
last letter, I rode for the first time to see the family at their own
house. The principal part of the road lay through retired narrow lanes,
beautifully overarched with groves of nut and other trees, which
screened the traveller from the rays of the sun, and afforded many
We are pleased to announce the availability of the following customer lists:
If you would like more information or a sample off any of our lists, please contact us at (905) 721-8456 or email us at repharm1(a)aol.com, Also we have the following lists as well
Below are just some of the lists available:
ERP (ENTERPRISE RESOURCE PLANNING):
MIDDLEWARE/CONNECTIVITY/APP SERVERS/WEB SERVERS:
SybaseCRM (CUSTOMER RELATIONSHIP MANAGEMENT):
Dot Com Directory
Chief Executive Officer
Chief Financial Officer
Chief Information Officer
INDUSTRY SPECIFIC LISTS:
Agriculture, Forestry and Fishing, Communications, Construction,
Finance, Insurance and Real Estate, Manufacturing, Mining, Public Administration,
Retail Trade, Services, Transportation,