On Tue, Jul 08, 2008 at 01:50:01PM +0100, Peter Bristow wrote:
> Hi Henning,
>
>
> > > what is needed to do for debuging here?
> >
> >
> > in general, you want to compile bgpd with debugging symbols (-g), then
> > attach gdb to the process that is the culprit (rde here), "cont" and
> > wait for the problem to show up. then get a backtrace ("bt").
> >
> > -
>
> Well it turns out that I suck at c debugging, on the other hand I've got a
> config that causes a crash on start reproducibly. I've submitted via
> sendbug, but there no guarantee I got that right so I thought I'd post here
> too.
>
> Config tar is at http://92.48.64.78/dump.tgz
>
> #bgpd -dv
> me = "92.48.95.195"
> hex_7600="92.48.95.1"
> the_7600="92.48.95.2"
> rs1="92.48.95.3"
> rs2="92.48.95.4"
> bs3_x450 = "92.48.95.5"
> Segmentation fault (core dumped)
> #
>
> Any thoughts would be great.
>
Fixed in -current. Your config triggers a parse error that caused the
crash. Now the output is:
# bgpd -n -f ./bgpd.conf
./serverNextHops.conf:121: Community is invalid (max: 65535)
For some reason the line number is off by one but the problematic line is:
network 217.112.94.232/31 set { nexthop 92.48.127.69 community 64667: }
--
:wq Claudio
