Possible issue with plugin loading #71

Closed
prymitive opened this Issue Nov 30, 2012 · 1 comment

Comments

Projects
None yet
1 participant
@prymitive
Contributor

prymitive commented Nov 30, 2012

Steps to reproduce:

  1. Use this buildconf to compile uWSGI
[uwsgi]
debug = true
main_plugin = 
plugins = dummy,corerouter
inherit = base
  1. run this command
./uwsgi --master --plugin 0:dummy -s :0

gdb show this:

max space for custom process name = 1755
[uwsgi-logger] registered "syslog"
[uwsgi-logger] registered "rsyslog"
[uwsgi-logger] registered "socket"
[uwsgi-logger] registered "redislog"
[uwsgi-logger] registered "mongodblog"
[uwsgi-logger] registered "file"
executable name: /home/lukasz.mierzwa/uwsgi_test/uwsgi
[uWSGI DEBUG] loading plugin 0:dummy

Program received signal SIGSEGV, Segmentation fault.
uwsgi_load_plugin (modifier=-1, plugin=0x7021f9 "corerouter", has_option=0x0) at core/plugins.c:72
72      void *uwsgi_load_plugin(int modifier, char *plugin, char *has_option) {
(gdb) where
#0  uwsgi_load_plugin (modifier=-1, plugin=0x7021f9 "corerouter", has_option=0x0) at core/plugins.c:72
#1  0x0000000000436358 in uwsgi_plugin_parse_section (filename=<value optimized out>) at core/plugins.c:17
#2  0x0000000000435e80 in uwsgi_load_plugin (modifier=<value optimized out>, plugin=<value optimized out>, has_option=0x0) at core/plugins.c:140
#3  0x0000000000436358 in uwsgi_plugin_parse_section (filename=<value optimized out>) at core/plugins.c:17
#4  0x0000000000435e80 in uwsgi_load_plugin (modifier=<value optimized out>, plugin=<value optimized out>, has_option=0x0) at core/plugins.c:140
#5  0x0000000000436358 in uwsgi_plugin_parse_section (filename=<value optimized out>) at core/plugins.c:17
#6  0x0000000000435e80 in uwsgi_load_plugin (modifier=<value optimized out>, plugin=<value optimized out>, has_option=0x0) at core/plugins.c:140
#7  0x0000000000436358 in uwsgi_plugin_parse_section (filename=<value optimized out>) at core/plugins.c:17
[same thing repeating]
#7486 0x0000000000435e80 in uwsgi_load_plugin (modifier=<value optimized out>, plugin=<value optimized out>, has_option=0x0) at core/plugins.c:140
#7487 0x000000000043fe26 in uwsgi_opt_load_plugin (opt=<value optimized out>, value=<value optimized out>, none=<value optimized out>) at core/uwsgi.c:3475
#7488 0x000000000041a17a in add_exported_option (key=0x457d4e "plugin", value=0x682320 "0:dummy", configured=0) at core/utils.c:2165
#7489 0x00000000004352eb in uwsgi_commandline_config () at core/init.c:180
#7490 0x0000000000444264 in main (argc=6, argv=0x7fffffffe6b8, envp=<value optimized out>) at core/uwsgi.c:1798

EDIT:

I've added corerouter to plugins list in my buildconf only because for some reason with command line from step 2 uWSGI was trying to load it:

[uWSGI DEBUG] loading plugin 0:dummy
open("./corerouter_plugin.so"): No such file or directory [core/utils.c line 4799]
!!! UNABLE to load uWSGI plugin: ./corerouter_plugin.so: cannot open shared object file: No such file or directory !!!
optind:6 argc:6

Now I see that corerouter is included in embedded_plugins list, so I have no idea why was it trying to load it as a separate plugin. I think that segfault is caused by me compiling corerouter both as embedded and separate plugin, if so than possible issue is the UNABLE to load uWSGI plugin: ./corerouter_plugin.so error. Anyway please take a look and decide if this is real issue

@prymitive

This comment has been minimized.

Show comment Hide comment
@prymitive

prymitive Apr 13, 2013

Contributor

closing as invalid, corerouter was both compiled in and loaded dynamically

Contributor

prymitive commented Apr 13, 2013

closing as invalid, corerouter was both compiled in and loaded dynamically

@prymitive prymitive closed this Apr 13, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment