|
Home > Archive > Unix Programming > March 2006 > Detecting Buffer overruns in apache modules
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Detecting Buffer overruns in apache modules
|
|
|
| Hi,
I am having an issue detecting a buffer overrun in my apache module. A
request to the handler executes successfully, but overwrites some
global memory that causes a segmentation error in the subsequent
request. Since the fault occurs in the subsequent request the core file
is not very useful in determining where the overwrite occurs.
I tried running apache under valgrind, but was unsuccessful due to a
valgrind bug (http://bugs.kde.org/show_bug.cgi?id=76223). Is there any
tool for FreeBSD 4.10 that I can use to detect static buffer overflows?
Any help is appreciated.
Thanks,
kjr
| |
| Igmar Palsenberg 2006-03-03, 6:43 pm |
| kjr wrote:
> I tried running apache under valgrind, but was unsuccessful due to a
> valgrind bug (http://bugs.kde.org/show_bug.cgi?id=76223). Is there any
> tool for FreeBSD 4.10 that I can use to detect static buffer overflows?
> Any help is appreciated.
Install a recent version of valgrind. That bug has been fixed ages ago.
If *BSD doesn't have any, you might try a Linux install, Apache is
generic enough for debugging this way.
Igmar
|
|
|
|
|