Bug 24691

Summary: map-mbone segfaults at getsockname
Product: Base System Reporter: Pekka Savola <pekkas>
Component: binAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 4.2-RELEASE   
Hardware: Any   
OS: Any   

Description Pekka Savola 2001-01-28 09:50:01 UTC
sixpack# map-mbone
warning - inconsistent metric/threshold for neighbor 0.0.0.0 of 128.214.231.22
warning - inconsistent metric/threshold for neighbor 0.0.0.0 of 212.226.250.2
warning - inconsistent metric/threshold for neighbor 0.0.0.0 of 193.94.248.145
warning - inconsistent metric/threshold for neighbor 0.0.0.0 of 130.230.1.1
warning - inconsistent metric/threshold for neighbor 0.0.0.0 of 130.230.1.1
warning - inconsistent metric/threshold for neighbor 0.0.0.0 of 130.230.1.1
warning - inconsistent metric/threshold for neighbor 0.0.0.0 of 130.230.1.1
warning - inconsistent metric/threshold for neighbor 0.0.0.0 of 130.230.1.1
warning - inconsistent metric/threshold for neighbor 0.0.0.0 of 130.230.1.1
Segmentation fault (core dumped)


# map-mbone -d 3
[snip dozens of lines]
SENT neighbor request 2 from 193.166.3.140   to 130.230.103.10
RECV neighbor list 2    from 193.10.252.94   to 193.166.3.140
warning - inconsistent metric/threshold for neighbor 0.0.0.0 of 193.10.252.94
SENT neighbor request   from 193.166.3.140   to 130.225.244.238
Bus error (core dumped)


The system is directly connected to mbone and 6bone.

Running 'gdb /usr/sbin/map-mbone map-mbone.core', it seems it crashed
at getsockname().  There is only one getsockname in mapper.c.

I believe this might only happen if you have IPv6 in use.

How-To-Repeat: See above.
Comment 1 Kris Kennaway freebsd_committer freebsd_triage 2003-07-13 06:48:59 UTC
State Changed
From-To: open->feedback

Does this persist in later releases?  If yes, please 
rebuild map-mbone and libc with debugging symbols: 
CFLAGS=-O -pipe -ggdb 
STRIP= 

and obtain a full traceback from gdb.
Comment 2 Kris Kennaway freebsd_committer freebsd_triage 2003-07-13 08:51:39 UTC
State Changed
From-To: feedback->closed

Submitter reports the bug can no longer be reproduced.