I can reproduce this on my computer with (much easier routing table and) 
the last iproute package from git.
(aka "20080417-1~git7422b80d3fa7517da3936fd298d3dd178fb7184a" which is the
latest upstream release not yet uploaded to debian, because of quality
concerns.)

Here's a backtrace:

(gdb) set args -r route
(gdb) run
Starting program: /home/gem/opt/iproute2/pkg-iproute/ip/ip -r route
10.99.99.0/24 dev fon  proto kernel  scope link  src 10.99.99.1
82.182.69.0/24 dev wan  proto kernel  scope link  src 82.182.69.4

Program received signal SIGSEGV, Segmentation fault.
0x0000000000427e92 in resolve_address (addr=0x7fff516ca980 "R�E\001\b", len=4,
    af=2) at utils.c:544
544             for (n = nht[hash]; n; n = n->next) {
(gdb) bt
#0  0x0000000000427e92 in resolve_address (addr=0x7fff516ca980 "R�E\001\b",
    len=4, af=2) at utils.c:544
#1  0x0000000000428081 in format_host (af=2, len=4, addr=0x7fff516ca980,
    buf=0x7fff516ca690 "82.182.69.4", buflen=256) at utils.c:598
#2  0x000000000040a1ad in print_route (who=0x7fff516ce930, n=0x7fff516ca958,
    arg=0x2abc59d4f780) at iproute.c:355
#3  0x0000000000425931 in rtnl_dump_filter (rth=0x6354c0,
    filter=0x4093d3 <print_route>, arg1=0x2abc59d4f780, junk=0, arg2=0x0)
    at libnetlink.c:238
#4  0x000000000040dcb9 in iproute_list_or_flush (argc=0, argv=0x0, flush=0)
    at iproute.c:1261
#5  0x000000000040e50a in do_iproute (argc=0, argv=0x7fff516cf9b0)
    at iproute.c:1438
#6  0x0000000000404af2 in do_cmd (argv0=0x7fff516d04ff "route", argc=1,
    argv=0x7fff516cf9a8) at ip.c:106
#7  0x0000000000405183 in main (argc=2, argv=0x7fff516cf9a0) at ip.c:252


Here's my route output:

[EMAIL PROTECTED]:~$ ip route
10.99.99.0/24 dev fon  proto kernel  scope link  src 10.99.99.1
82.182.69.0/24 dev wan  proto kernel  scope link  src 82.182.69.4
default via 82.182.69.1 dev wan
[EMAIL PROTECTED]:~$ ip -r route
10.99.99.0/24 dev fon  proto kernel  scope link  src 10.99.99.1
82.182.69.0/24 dev wan  proto kernel  scope link  src 82.182.69.4
Segmentation fault



I'll look closer at the cause when I get a chance!

--
Regards,
Andreas Henriksson






-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to