From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Jason@zx2c4.com Received: from frisell.zx2c4.com (frisell.zx2c4.com [192.95.5.64]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 576544c2 for ; Sun, 6 Nov 2016 10:53:34 +0000 (UTC) Received: by frisell.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 540c07b1 for ; Sun, 6 Nov 2016 10:53:34 +0000 (UTC) Received: by frisell.zx2c4.com (ZX2C4 Mail Server) with ESMTPSA id 5fa9493b (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128:NO) for ; Sun, 6 Nov 2016 10:53:34 +0000 (UTC) Received: by mail-lf0-f47.google.com with SMTP id t196so93877452lff.3 for ; Sun, 06 Nov 2016 02:55:10 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: <25241985.20161106100258@vodka.home.kg> <1289478110.20161106110707@vodka.home.kg> From: "Jason A. Donenfeld" Date: Sun, 6 Nov 2016 11:55:07 +0100 Message-ID: To: k@vodka.home.kg Content-Type: text/plain; charset=UTF-8 Cc: WireGuard mailing list Subject: Re: [WireGuard] mips32 crash List-Id: Development discussion of WireGuard List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Strange, spam filters don't like your domain. Got the message. Analyzing now. Think you could "instrument" where you think the crash happens with a bunch of printks?