etch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Marsh (Created) (JIRA)" <>
Subject [jira] [Created] (ETCH-186) Jenkins hash routines pollute C namespace
Date Fri, 07 Oct 2011 22:33:29 GMT
Jenkins hash routines pollute C namespace

                 Key: ETCH-186
             Project: Etch
          Issue Type: Bug
          Components: c-binding
         Environment: All Linux/POSIX/SVr4 environments should be affected
            Reporter: Thomas Marsh
            Priority: Blocker

hcreate and hdestroy are defined in libc on Linux, but are also used as primary entry points
into the jenkins hash table routines. Normally this is not a problem, but the linkage is broken
when, for example, embedding etch inside a Python module, and hash routines fail. In general,
the jenkins hash routines are too generically named to be safe for linking and dynamic loading
(names like "hdel", "hadd", "hfind", "hfirst", and many, many more).

[tmarsh]$ nm /lib/  | egrep hcreate
00a0dd50 t __GI_hcreate_r
00a0daa0 T hcreate
00a0dd50 T hcreate_r
[tmarsh]$ nm src/main/ | egrep hcreate
0003e560 T hcreate
[tmarsh@dasher c]$ 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message