i've this problem on a sparc64 ... :-| i'll try the debug ...
thx Thomas On Thursday 14 December 2006 12:15, Stuart Henderson wrote: > On 2006/12/14 10:44, [EMAIL PROTECTED] wrote: > > > > the core dump is here > > > > http://www.tbits.org/snmpd.core.gz > > first: if you built the port yourself, try running from a binary > package to rule out compilation errors. if that doesn't help... > this seems easily repeatable, so recompile the port with debugging > (assuming the port honours CFLAGS: "make clean; CFLAGS=-g make", then > either reinstall or just run snmpd from the port build directory). > > get it to dump core then run 'gdb snmpd snmpd.core', type 'bt' > which should display where in the source code the error occurred. > by itself the core file is not very useful; the information > from this backtrace is a lot better. > > if the output of that doesn't give sufficient clues to track it > down yourself, send the output to the maintainer (run 'make > show=MAINTAINER' in the port directory) along with more details > about what you're running: which version of the port/package, > machine arch, OpenBSD version - the last two are best satisfied > by sending a dmesg. > > fwiw I have vlans numbered higher than 10 on OpenBSD/i386 boxes > running snmpd with no problem. I don't recall trying it on any of > my sparc64 or arm (strict alignment architectures where non- > portable code is fairly likely to produce bus errors).
