<br><div><span class="gmail_quote">2007/5/7, Florian Forster <<a href="mailto:octo@verplant.org">octo@verplant.org</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I don't have a FreeBSD box to test the code on, so it's not surprising<br>that there are bugs in the code :/<br><br>By far the most useful information with a problem like this is, as<br>Sebastian has pointed out, a stack backtrace which you can get by
<br>building collectd with `--enable-debug' and then run the daemon from<br>a debugger. Alternatively you can have the daemon write a coredump<br>(using the bash-builtin `ulimit' or whatever mechanismn your shell uses)
<br>and analyse that with a debugger.<br></blockquote></div><br>Good evening everyone,<br><br>Well... sometimes... Computers make you feel really silly (or crazy)...<br><br>I tried to get more informations yesterday about this bug, without great results (clean directory, compile in debug mode, unload every plugins, and try to get something with gdb).
<br><br>And this morning, when I build a "debug mode" enabled collectd, to provide you more infos about this, I did not get the segmentation fault error (with main plugins loaded : cpu,disk,net). Everything run fine... :-S
<br><br>So... I stay in touch, and I will be glad to give you a hand with collectd on freebsd.<br><br>Regards,<br><br>Julien<br><br>