[Quagga-bugs] [Bug 392] BGPD crashes with bgpd in free()

[bugzilla-daemon at allevil.dishone.st]

Please do not reply directly to this email. All additional  
comments should be made in the comments box of this bug  
report.  
  
http://bugzilla.quagga.net/show_bug.cgi?id=392  
  




------- Additional Comments From gert at greenie.muc.de  2007-08-14 13:06 -------
Hi,

my test config for "immediate crash" is this one:

--------------------------------------------------------
!
! Zebra configuration saved from vty
!   2007/07/20 14:10:26
!
hostname ns3-base
password XXX
enable password YYY
!
router bgp 65300
 bgp router-id 193.149.44.250
 network 193.149.44.49/32
 neighbor 193.149.44.253 remote-as 5539
 neighbor 193.149.44.253 route-map set-no-export out
!
route-map set-no-export permit 10
 set community no-export
!
!
-------------------------------------------------------

with this, I get the "assert" type of crash:

(gdb) run -f bgpd.conf
Starting program: /var/tmp/quagga-0.99.8/bgpd/bgpd -f bgpd.conf

Program received signal SIGABRT, Aborted.
0x00000000407206a8 in kill () from /lib/libc.so.6
(gdb) where
#0  0x00000000407206a8 in kill () from /lib/libc.so.6
#1  0x000000004071f0d4 in abort () from /lib/libc.so.6
#2  0x000000000015d5d0 in _zlog_assert_failed (
    assertion=0x1a5258 "(((s)->endp) <= (s)->size)", file=0x1a5178 "stream.c", 
    line=191, function=0x1a4ed0 "stream_get_endp") at log.c:605
#3  0x0000000000159fb4 in stream_get_endp (s=0x46e200) at stream.c:191
#4  0x0000000000128340 in bgp_write (thread=0x7fdffffea00) at bgp_packet.c:633
#5  0x00000000001539b0 in thread_call (thread=0x7fdffffea00) at thread.c:1051
#6  0x0000000000102d84 in main (argc=3, argv=0x7fdffffec90) at bgp_main.c:323

looking at "s", I agree that it looks fishy:

(gdb) up
#3  0x0000000000159fb4 in stream_get_endp (s=0x46e200) at stream.c:191
191       STREAM_VERIFY_SANE(s);
(gdb) print s
$1 = (struct stream *) 0x46e200
(gdb) print *s
$2 = {next = 0x0, getp = 0, endp = 4734976, size = 0, data = 0x46e280 ""}

  
  
  
  
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.