Bug 86521

Summary: Enhancement: eCos should have proper dynamic loading
Product: [Retired] eCos Reporter: Jonathan Larmour <jifl-bugzilla>
Component: OtherAssignee: Jonathan Larmour <jifl-bugzilla>
Status: CLOSED WONTFIX QA Contact: Jonathan Larmour <jifl-bugzilla>
Severity: medium Docs Contact:
Priority: low    
Version: CVSKeywords: FutureFeature
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-06-20 16:22:18 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jonathan Larmour 2003-03-25 01:28:07 UTC
This is an enhancement requested at FOSDEM 2003. Here's an excerpt from a
relevant mail:

  * Dynamic loading. A full blown implementation is of course quite large and a
can of worms. So two possibilities were suggested - a system similar to what
vxWorks does where objects are linked but still with relocs (essentially a .o
file) and linking at the time the .o is loaded by comparing with a built-in
symbol table and filling in the relocs (and adding newly exported symbols from
the new object to the symbol table too). Presumably some sort of init function
with a unique name to that object would want to be called too.

  A second possibility (and it isn't either/or - both are possible) would be a
very simple system using function pointer tables and stubs - for those who just
want dynamically updatable code rather than more complex dynamic loading.

Comment 1 Alex Schuilenburg 2003-06-20 16:22:18 UTC
This bug has moved to http://bugs.ecos.sourceware.org/show_bug.cgi?id=86521