Re: Recent ifconfig changes choke on fwip

Daniel O'Connor wrote:

>On Fri, 10 Dec 2004 13:00, Daniel O'Connor wrote:
>  
>
>>I tried to do some tracing in GDB the line numbers don't seem to match up
>>properly :-/
>>    
>>
>
>Ahh, building without -O2 helps..
>(gdb) bt
>#0  0x0804b57a in in_status (s=7, info=0x805a134) at /usr/src/sbin/ifconfig/af_inet.c:69
>#1  0x0804a046 in af_all_status (s=7, sdl=0x805a134) at /usr/src/sbin/ifconfig/ifconfig.c:405
>#2  0x0804af39 in status (afp=0x80563c0, addrcount=0, sdl=0x805a134, ifm=0x805a0d4, ifam=0x0)
>    at /usr/src/sbin/ifconfig/ifconfig.c:850
>#3  0x08049e05 in main (argc=0, argv=0xbfbfe914) at /usr/src/sbin/ifconfig/ifconfig.c:349
>
>(gdb) list af_inet.c:69
>64
>65              sin = (struct sockaddr_in *)info->rti_info[RTAX_IFA];
>66              if (sin == NULL)
>67                      return;
>68
>69              printf("\tinet %s ", inet_ntoa(sin->sin_addr));
>70
>71              if (flags & IFF_POINTOPOINT) {
>72                      /* note RTAX_BRD overlap with IFF_BROADCAST */
>73                      sin = (struct sockaddr_in *)info->rti_info[RTAX_BRD];
>(gdb) print sin
>$3 = (struct sockaddr_in *) 0xfe
>(gdb) print info->rti_info
>$4 = {0x100590, 0x70697766, 0xc04f4330, 0xa4170800, 0xff020a38, 0xfe, 0x0, 0x0
>  
>

I don't have any firewire devicesto test with.  Someone else will need 
to pickup this one.

    Sam