unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
* mod_guile, Apache and regexps
@ 2002-07-25  2:17 Dale P. Smith
  0 siblings, 0 replies; only message in thread
From: Dale P. Smith @ 2002-07-25  2:17 UTC (permalink / raw)


Hello List,

I have an interesting problem, that I'm not at all sure how to resolve.

Clinton Ebadi pointed out that mod_guile gets segv's and memory
allocation errors when using regular expressions.  It turns out that
libguile is linked against glibc (my system is Debian Linux (sid) ) and
regcomp and regexec are resolved from there.  The apache executable
already provides functions with the exact same names, and when mod_guile
is loaded (and the regexec routines in libguile are called), regcomp and
regexc are resolved to the apache functions and not the libc ones.

Well, so what.  The problem is that the structures used are different.
When the code in libguile/regexp-posix.c accesses the ->re_nsub member,
it thinks it's accessing an int, but it's probably accessing the address
of a buffer or something. So instead of allocating a few bytes, it's
allocating 0x5a000084 * sizeof(struct regex_t) bytes.

So.  Is there a way to force libguile to resolve against glibc when it's
dynamically loaded into the running apache?

BTW: mod_guile is at http://savannah.gnu.org/projects/mod-guile/

Thanks!
  -Dale

-- 
Dale P. Smith
Senior Systems Consultant,      | Treasurer,
Altus Technologies Corporation  | Cleveland Linux Users Group
dsmith@altustech.com            | http://cleveland.lug.net
440-746-9000 x339               |

_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2002-07-25  2:17 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-07-25  2:17 mod_guile, Apache and regexps Dale P. Smith

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).