While it is probably not a good idea to have a GVC config that is 100000 bytes,
I see no reason it should be arbitrarily rejected. In future, it might be a good
idea to make `gvconfig_plugin_install_from_config` accept a file pointer instead
of a string and read/parse the config file incrementally. If this were done,
then there would probably be no issue at all with large configs.
- Check for existence of `dl_iterate_phdr(3)` and if it is available, prefer
using it instead of iterating over `/proc/self/maps` for computing `libdir`.
+- A limit on GVC config files of 100000 bytes has been removed.
### Fixed
char *libdir;
char *config_file_name = GVPLUGIN_CONFIG_FILE;
-#define MAX_SZ_CONFIG 100000
#endif
/* builtins don't require LTDL */
/* silently return without setting gvc->config_found = TRUE */
return;
}
- else if (config_st.st_size > MAX_SZ_CONFIG) {
- agerr(AGERR,"%s is bigger than I can handle.\n", gvc->config_path);
- }
else {
f = fopen(gvc->config_path,"r");
if (!f) {