On Mon, Apr 17, 2000, Martin Cracauer wrote:
j
> > I have exactly the same problem hacking squid code under 4.0-CURRENT
> > and 5.0-CURRENT. Basically, inside the dns routines a variable
> > would be corrupted between a couple of non-relevant lines, and cause
> > squid to segfault after trying to resolve anything. Taknig out -O2
> > and replacing it with -O causes the same problem. Its annoying. :(
>
> Could you pleaseverify whether that looks like PR bin/16862?
>
> If they are releated, you need to change the optimization setting of
> the shared libraries (or generally -fpic code) your crashing code
> uses, not the setting of the code itself. Raising the optimization
> setting may as well help as lowering it.
>
> Basically, our gcc produces code our as doesn't understand and symbol
> locations in -fpic code may be damaged, so that access (read or write)
> to such a variable causes segmentation violations.
>
> Are there any as warning messages (especially GOTOFF - related ones)
> when you compile the code in question, especially when compiling
> shared libraries it may use?
>
> It sounds like you found the lines where the corruption happens, I
> would welcome the exact locations. I'd like to hunt this one down.
>
Its squid's DNS routines, not the shared libraries.
heck the squid-dev archies on http://www.squid-cache.org/, as someone
found the lines of asm which are wrongly generated.
Adrian
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
