From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: None (mailfrom) identity=mailfrom; client-ip=8.23.224.60; helo=out.smtp-auth.no-ip.com; envelope-from=kevin@carhart.net; receiver= Received: from out.smtp-auth.no-ip.com (smtp-auth.no-ip.com [8.23.224.60]) by hurricane.the-brannons.com (Postfix) with ESMTPS id 0884477AAF for ; Tue, 27 Feb 2018 01:32:11 -0800 (PST) X-No-IP: carhart.net@noip-smtp X-Report-Spam-To: abuse@no-ip.com Received: from carhart.net (unknown [99.52.200.227]) (Authenticated sender: carhart.net@noip-smtp) by smtp-auth.no-ip.com (Postfix) with ESMTPA id 804021AD for ; Tue, 27 Feb 2018 01:33:23 -0800 (PST) Received: from carhart.net (localhost [127.0.0.1]) by carhart.net (8.13.8/8.13.8) with ESMTP id w1R9XMmF006139 for ; Tue, 27 Feb 2018 01:33:22 -0800 Received: from localhost (kevin@localhost) by carhart.net (8.13.8/8.13.8/Submit) with ESMTP id w1R9XMJM006136 for ; Tue, 27 Feb 2018 01:33:22 -0800 Date: Tue, 27 Feb 2018 01:33:21 -0800 (PST) From: Kevin Carhart To: Edbrowse-dev@lists.the-brannons.com In-Reply-To: <20180126144402.eklhad@comcast.net> Message-ID: References: <20180126144402.eklhad@comcast.net> User-Agent: Alpine 2.03 (LRH 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: [Edbrowse-dev] css in C X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.25 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Feb 2018 09:32:12 -0000 This is great! > dbcss can help in this regard, dumps lots of information to /tmp/css If I make a list of all of the new debugging functionality, can you tell me if I'm missing any? dber - you toggle this from the edbrowse command line dbcss - is this a toggle also? ^> - the file redirect to your filesystem showscripts - list all scripts searchscripts - searches all scripts for a string debugEvent - toggles diagnostic messages about events - to get this, you set the boolean variable to true and recompile debugClone - you also enable this by recompiling startwindow demin aloop jdb db# And on this subject, there's something else you implemented recently and I haven't taken advantage of it yet. It's the hex prefixes that show when event handler code fails, usually near the end of the output after the regular .js files have finished. Such as, error in f575d3.ontimer() It seems like excellent information, so how would you go about cross referencing? Can we go from this message, to a key where you can find out that f575d3 is a certain element? And then from that point, maybe the element has an obscure string on it that you can look for with searchscripts(), or you can get your bearings based on f575d3 and its position in the tree. It seems like a getElementsByEventListener("ontimer") would be useful. That would be another way of narrowing it down. "I know from the error message that a timer fails, so now I have the result set of five elements that listen for this. It must be one of these." This could be either another getElements function or maybe there is something among the selector syntax to do it! thanks Kevin