From muks@isc.org Thu Aug 3 03:11:53 2017 MIME-Version: 1.0 To: bind-suggest@isc.org X-Original-To: bind9-public@bugs.isc.org User-Agent: Mutt/1.8.3 (2017-05-23) From: "Mukund Sivaraman" Date: Thu, 3 Aug 2017 08:41:46 +0530 Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.64.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx.pao1.isc.org", Issuer "COMODO RSA Organization Validation Secure Server CA" (not verified)) by bugs.isc.org (Postfix) with ESMTPS id 5623CD78AFB for ; Thu, 3 Aug 2017 03:11:53 +0000 (UTC) Received: from mail.banu.com (mail.banu.com [IPv6:2a01:4f8:140:644b::225]) by mx.pao1.isc.org (Postfix) with ESMTP id 029EC34C0FB for ; Thu, 3 Aug 2017 03:11:50 +0000 (UTC) Received: from jurassic (unknown [115.118.24.244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.banu.com (Postfix) with ESMTPSA id DFEBD56A07BF; Thu, 3 Aug 2017 03:11:48 +0000 (GMT) Subject: Include fctx in fetchevent X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on mx.pao1.isc.org content-type: text/plain; charset="utf-8" X-RT-Incoming-Encryption: Not encrypted Delivered-To: bind9-public@bugs.isc.org Return-Path: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.0 Message-ID: <20170803031146.GA24147@jurassic> Content-Disposition: inline X-RT-Original-Encoding: ascii X-RT-Interface: Email Content-Length: 293 When a fetchevent gets delivered, the fetch context associated with it (which contains a lot of useful information such as fctx->rmessage) isn't available to the callback. This is inconvenient for debugging purposes, and we should include this pointer within the fetchevent struct. Mukund