OpenBSD 3.8: Segmentation Fault (Core Dumped) (1.1beta5)

[cameronsto]

When running 'zabbix_agentd -p' I get the error Segmentation Fault (Core Dumped). When I load up the dump file in gdb it says:

#0  0x1c00c1d7 in PROC_MEMORY (cmd=0xcfbe7ba0 "proc.mem", param=0x1 "\t¾Ó\036", flags=1, result=0xcfbe93e0) at proc.c:158
158                                             value = proc[i].kp_proc.p_vmspace->vm_tsize

With the following backtrace information:

#0  0x1c00c1d7 in PROC_MEMORY (cmd=0xcfbe7ba0 "proc.mem", param=0x1 "\t¾Ó\036", flags=1, result=0xcfbe93e0) at proc.c:158
#1  0x1c0067af in process (in_command=0x89418390 "proc.mem", flags=1, result=0xcfbe93e0) at common/common.c:468
#2  0x1c0062e4 in test_parameters () at common/common.c:315
#3  0x1c005bc0 in main (argc=2, argv=0xcfbe9540) at zabbix_agentd.c:509

For reference this doesn't happen when running the same command on OpenBSD 3.7 using 1.1beta5.

Any ideas?

-cameron

[Alexei]

Thanks for the information. Will try to look at this as soon as we get access to OpenBSD 3.8 box.

[cameronsto]

I can set one up with SSH access for you guys if that would help. It would be running on my home cable connection but it's plenty fast over SSH. I use OpenBSD frequently and while not all items are supported (which I'm ok with) i'd prefer to not have the possibility of a seg fault in the code.

Let me know. Thanks.

-cameron

[Alexei]

Please, send SSH access details to [email protected]. Give us a couple of days. Many thanks!

[cameronsto]

Well, I was setting up the box for you and was going to go ahead and compile zabbix to get everything ready and...it seems to work fine. No segmentation fault. I'll reload the OS on my other box that's causing issues and see if I run into the problem again.

I'll update this thread again if I have issues after re-installing.

-cameron

[cameronsto]

Small update on this. On my box that is giving me problems, when I run "zabbix_agentd -p" as my personal account on the box it runs fine. If I su to root and run it I get the segmentation fault. I'm going to try this on the other box I setup and see if it's the case there too.

-cameron