I knew it was a stupid question :-) Thing is, it's not happening on another box, with a similar installation, and the same code base, so I'm suspecting something environment oriented, odd libraries or the like. The major thing that's different is the modperl installation - which I installed against apache manually, under SuSe 10, instead of using the standard Debian package install which the working box uses, for various reasons. And modperl doesn't work, so I'm suspecting either I've messed something up, or modperl has. I'm clearly more likely to be at fault here, but it's very wierd behaviour, so I thought someone else might have come across it before.
R. On Wednesday 22 November 2006 17:42, Michael Peters wrote: > > Richard Foley wrote: > > On Wednesday 22 November 2006 16:21, Michael Peters wrote: > >> I've never seen anything like this before. Does it happen with all of your > >> modules or just some of them. > >> > > I'm only noticing it with a couple of modules out of a batch of perhaps a > > thousand... > > > >> Are you using source filters? > >> > > I don't think so. > > > >> Or are you using modules with source filters (like Switch)? > >> > > Well, I was about to say no, I'm not using Switch, but then I checked :-\, and > > yes, it appears some of the code uses Switch. Now I'm not sure this has an > > effect because Switch is not loaded at the time I can see the truncated > > library, but maybe something related is happening. > > Well, Switch is just one library that uses source filters. > > > What makes you think it's a "module with a source filter" issue of some kind? > > If it's not a daft question ?-) > > Source filters actually alter the source code. It's not just doing symbol table > manipulation or changing the parsing rules. It's actually parsing your code and > changing it. If some code has something that the filter's parser can't deal > with, strange things can happen. > -- Richard Foley Ciao - shorter than aufwiedersehen http://www.rfi.net/
