From owner-freebsd-current@freebsd.org  Sun Jun 25 02:10:09 2017
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 55E44D8678E
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Sun, 25 Jun 2017 02:10:09 +0000 (UTC) (envelope-from null@pozo.com)
Received: from pozo.com (pozo.com [50.197.129.137])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "pozo.com", Issuer "pozo.com" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id 31EE98009E
 for <freebsd-current@freebsd.org>; Sun, 25 Jun 2017 02:10:08 +0000 (UTC)
 (envelope-from null@pozo.com)
Received: from 50-197-129-138-static.hfc.comcastbusiness.net (octo.pozo.com
 [192.168.0.2]) (authenticated bits=128)
 by pozo.com (8.15.2/8.15.2) with ESMTPA id v5P28SHo063458;
 Sat, 24 Jun 2017 19:08:28 -0700 (PDT) (envelope-from null@pozo.com)
From: Manfred Antar <null@pozo.com>
Message-Id: <EA888ADF-AF3F-4DEF-BC91-8E5EA8176A83@pozo.com>
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Current amd64 new error or warning from today's current with ruby
 r320323
Date: Sat, 24 Jun 2017 19:08:28 -0700
In-Reply-To: <20170625015504.GX1467@albert.catwhisker.org>
Cc: FreeBSD Current <freebsd-current@freebsd.org>
To: David Wolfskill <david@catwhisker.org>
References: <44028FBF-C8B1-4A69-B798-F4E28CFCD779@pozo.com>
 <20170625012359.GS3437@kib.kiev.ua>
 <040BF7D1-2FDF-415B-9A17-ADD608503F14@pozo.com>
 <20170625015504.GX1467@albert.catwhisker.org>
X-Mailer: Apple Mail (2.3273)
X-Spam-Status: No, score=-102.9 required=5.0 tests=ALL_TRUSTED,BAYES_00,
 HTML_MESSAGE,RP_MATCHES_RCVD,USER_IN_WHITELIST autolearn=ham
 autolearn_force=no version=3.4.1, No
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on pozo.com
X-pozocom-MailScanner-Information: Please contact the ISP for more information
X-pozocom-MailScanner-ID: v5P28SHo063458
X-pozocom-MailScanner: Found to be clean
X-pozocom-MailScanner-From: null@pozo.com
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable
X-Content-Filtered-By: Mailman/MimeDel 2.1.23
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Jun 2017 02:10:09 -0000


> On Jun 24, 2017, at 6:55 PM, David Wolfskill <david@catwhisker.org> wrote:
>=20
> On Sat, Jun 24, 2017 at 06:48:03PM -0700, Manfred Antar wrote:
>> ...=20
>>> ktrace your failing ruby invocation, then post output of kdump -H somew=
here.
>>>=20
>>=20
>> Ok not sure  if this is right , but this is what i did:
>>=20
>> (tmp)4637}ktrace /usr/local/bin/ruby -v
>=20
> You might want to re-do that, specifying the "-di" flags to ktrace (if
> the output fails to include activities from child processes, and tracing
> those is of interest).

Ok did:
ktrace -di /usr/local/bin/ruby -v

kdump -H -f ./ktrace.out >kdump-new.txt

File is at :

http://www.pozo.com/kernel/kdump-new.txt <http://www.pozo.com/kernel/kdump-=
new.txt>

smaller than the first one.

Manfred
--=20
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.