[OLSR-users] httpinfo

[Andrew Hodel]

Attached are the following files:

olsrd - olsrd executable
httpinfo - httpinfo plugin
nameservice - nameservice
olsrd.conf - config file
olsrd_output - output of olsrd during crash

The program doesn't segfault, it just says "done".  This is olsrd
0.4.9 built as you described from sources I got from olsr.org today.

kill -s SIGSEGV $$ creates a core file in cwd (or wherever
core_pattern specifies)

I reproduce this problem by going to the httpinfo page, viewing a few
pages, then clicking my browser bookmark as fast as I can (effectively
refreshing the page).  After about 5 seconds it just dies.

btw, I did not forget "ulimit -c unlimited", I tried to produce a core
file more then once.
(spam-protected):/home/zip # ulimit
unlimited

Keep me updated, if there is anything else you need just ask.




Andrew


On 6/14/05, Thomas Lopatic <(spam-protected)> wrote:
> Hi Andrew,
> 
> Thanks for reporting this. Yes, we should definitely do something about
> this! I'd like to ask you to do the following. (Maybe we should put this
> onto the olsr.org site? This seems to become a FAQ.) I assume that you
> build olsrd yourself and that you're working on Linux.
> 
> 1. Change to the olsrd source code directory.
> 
> 2. Say "make OS=... uberclean; make OS=..." to force a complete rebuild
> and to build olsrd.
> 
> 3. Do NOT say "make install". "make install" would strip the debug symbols
> from the compiled executable and from the plug-ins in order to reduce the
> size of the executables and the plug-ins. But we need the debug symbols.
> 
> 4. Manually copy the olsrd executable and the plug-in .so files to the
> appropriate directories. ("/usr/sbin" and "/usr/lib" by default)
> 
> 5. You now have an olsrd executable with debug information and plug-ins
> with debug information installed.
> 
> 6. Say "ulimit -c unlimited". This will allow olsrd to dump core.
> 
> 7. Run olsrd and make it crash.
> 
> 8. Create a TAR of the (1) olsrd executable, (2) the plug-in .so files,
> (3) the core file, and send it to me. This will enable me to find out
> where exactly the crash happens.
> 
> Thanks,
> -Thomas
> 
> _______________________________________________
> olsr-users mailing list
> (spam-protected)
> https://www.olsr.org/mailman/listinfo/olsr-users
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: olsrd_crash.tar
Type: application/x-tar
Size: 1361920 bytes
Desc: not available
URL: <http://lists.olsr.org/pipermail/olsr-users/attachments/20050614/55b4a8f3/attachment.tar>