[uClinux-dev] busybox ping in latest release

David McCullough davidm at snapgear.com
Sun Oct 30 18:13:14 EST 2005


Jivin Matt Waddel lays it down ...
> Hi,
> 
> Simple question 1st - more detail below.
> ---------------------------------------
> Has anybody tried the busybox ping with the fancy option output
> set in the latest 2.6.12 kernel release?
> 
> More detail.
> ------------
> 
> I'm using the 20050906 release with the 2.6.12-uc0 kernel.  The
> platform is the M5208EVB.
> 
> When I ping with the SIZE value set to between 6 and 11
> everything works great.
> 
> # ping -s 11 172.27.0.145
> PING 172.27.0.145 (172.27.0.145): 11 data bytes
> 19 bytes from 172.27.0.145: icmp_seq=0 ttl=64 time=3.1 ms
> 19 bytes from 172.27.0.145: icmp_seq=1 ttl=64 time=0.7 ms
> 19 bytes from 172.27.0.145: icmp_seq=2 ttl=64 time=0.7 ms
> 
> --- 172.27.0.145 ping statistics ---
> 3 packets transmitted, 3 packets received, 0% packet loss
> round-trip min/avg/max = 0.7/1.5/3.1 ms
> 
> When I set the size to a greater value I get the following:
> 
> # ping -s 12 172.27.0.145
> PING 172.27.0.145 (172.27.0.145): 12 data bytes
> 20 bytes from 172.27.0.145: icmp_seq=0 ttl=64 time=2.2 ms
> Illegal instruction
> 
> I don't think the "Illegal instruction" message is valid.
> I've traced the source of this message to the kernel/traps.c
> file to VEC_LINE11.  I'm not sure what VEC_LINE11 is, but I
> don't think it's the root cause of this problem.

No it's not the cause,  you are most likely seeing some memory
corruption due to a buffer overflow or stack overflow, the the resulting
corrupted code is causing and "Illegal instruction" trap.

Short or debugging it and fixing it,  not many other options. You
could try switching to iputils ping ?

Cheers,
Davidm

-- 
David McCullough, davidm at cyberguard.com.au, Custom Embedded Solutions + Security
Ph:+61 734352815 Fx:+61 738913630 http://www.uCdot.org http://www.cyberguard.com



More information about the uClinux-dev mailing list