Re: kern/51450 (tcptraceroute stopped working properly in 6.0 -> 7.0 transition)

[<Paul_Koning%Dell.com@localhost>]

The following reply was made to PR kern/51450; it has been noted by GNATS.

From: <Paul_Koning%Dell.com@localhost>
To: <gnats-bugs%NetBSD.org@localhost>
Cc: <kern-bug-people%netbsd.org@localhost>, <netbsd-bugs%netbsd.org@localhost>,
	<gnats-admin%netbsd.org@localhost>, <he%NetBSD.org@localhost>
Subject: Re: kern/51450 (tcptraceroute stopped working properly in 6.0 ->
 7.0 transition)
Date: Tue, 30 Aug 2016 14:03:29 +0000

 > On Aug 30, 2016, at 9:59 AM, <he%NetBSD.org@localhost> <he%NetBSD.org@localhost> wrote:
 >=20
 > Synopsis: tcptraceroute stopped working properly in 6.0 -> 7.0 transition
 >=20
 > State-Changed-From-To: open->closed
 > State-Changed-By: he%NetBSD.org@localhost
 > State-Changed-When: Tue, 30 Aug 2016 13:59:34 +0000
 > State-Changed-Why:
 > Problem fixed; was wrong types in evel/libnet10 (not explictly sized),
 > causing an LP64 bug.  So not a kern bug after all.
 
 Are the relevant struct packed?  If not, might there be other instances of =
 this issue caused by target-dependent struct padding?  For example, I remem=
 ber that the default alignment for some data types (like int64_t) is differ=
 ent on Intel than on RISC processors.
 
 	paul