Irssi core bugs

Notice: Undefined index: tasklist_type in /var/www/ : eval()'d code on line 85 Notice: Undefined index: tasklist_type in /var/www/ : eval()'d code on line 90
  • Status Unconfirmed
  • Percent Complete
  • Task Type Bug Report
  • Category core
  • Assigned To No-one
  • Operating System Linux
  • Severity Medium
  • Priority Normal
  • Reported Version Irssi SVN
  • Due in Version Undecided
  • Due Date Undecided
  • Votes 0
  • Private No
Attached to Project: Irssi core bugs
Opened by jt (jt) - 2013-07-14

FS#895 - module function namespace collisions

This is a problem that occurs due to the way modules are loaded. A function with the same name in two modules will always call the function in the first module, even if you call this function from the second module.

I created two modules, and I was running into a situation where functionality in the second one was not working when the first was loaded. I ended up tracking this down to that functions from modules are loaded into a global namespace.

So if you define a function my_function() in module1.c, and load module1, and define a function with the same name, my_function(), in module2.c, and load module2, then calls to my_function() from module2 will actually call module1's my_function().

This is a bit confusing as there are no errors reported or anything about this collision.

I was able to confirm that this happened for functions both called in the module_init() function, and functions called from other places, such as in signal callbacks.

The reason this seems to occur is how the modules are loaded: in core/modules-load.c module_open() we call:

module = g_module_open(path, (GModuleFlags) 0);

If we look at the available flags for this function:

it appears that the default is to have the functions all put into a global namespace. If we change the g_module_open() calls to pass the flag G_MODULE_BIND_LOCAL, the problem goes away.

However, whether this is a true bug or whether it was designed this way for some reason I am not sure. I found it fairly confusing but I suppose it could be something that was intended and I just did not find documentation to that effect.

It can be worked around by trying to keep function names unique in your module against all other modules, though if someone were to have many modules I suppose that could get error prone.

To reproduce this, one can create two bare modules and have a function with the same name in both, and call the function with the same name from the <module>_init() function - for example to print out the name of the module. I can provide such example modules if necessary.

I have a patch for this which I will attach.

This task does not depend on any other tasks.