bug-inetutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug-inetutils] [sr #104441] inetuils 1.4.2 on sparc


From: William Harrington
Subject: [bug-inetutils] [sr #104441] inetuils 1.4.2 on sparc
Date: Thu, 28 Jun 2007 23:54:06 +0000
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.2) Gecko/20070222 SeaMonkey/1.1.1

Follow-up Comment #4, sr #104441 (project inetutils):

I have something interesting regarding the problems in the previous
comments.

I have noticed that with glibc-2.4 it will work fine. With glibc-2.5/2.6 the
code is the same with memcpy and wordcopy, yet the bus error still occurs at
the memcpy.

What I have done is include the memcpy code from memcpy.c from the glibc 2.6
tree and also have wordcopy.c build along with the objects. What happens is a
ping that works.

Here is what I have done so far in my debugging of the code. What sparked my
curiosity was in netkit-base-0.17 ping util, the code that glibc memcpy (or
maybe it is actually wordcopy) does is in the ping source code. This may be a
glibc bug or an unexpected return from glibc for ping. I'm not sure of the
exact flow of things. Maybe this info will help.

Here is a link to the patch I use at this current time:

http://berzerkula.no-ip.org/patches/inetutils-1.5-memcpy_sparc64.patch

Basically it puts memcpy function into ping.c
It creates wordcopy.c (from glibc-2.6)
It creates memcpy.h (from glibc-2.6)
It creates pagecopy.h (from glibc-2.6)

With the patch these are the values of &tv1, tp, and tv1:

&tv1: -3109200     tp: 2136700     tv1: 056

Without the patch these are the values of &tv1, tp, and tv1:

&tv1: -5624144     tp: 2136700     tv1: 0

Hope this helps some. If the patch link doesn't work, leave me an address to
email it.

Sincerely,

William Harrington

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/support/?104441>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/





reply via email to

[Prev in Thread] Current Thread [Next in Thread]