From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23798 invoked by alias); 4 Apr 2010 23:25:01 -0000 Received: (qmail 23773 invoked by uid 22791); 4 Apr 2010 23:24:57 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (38.113.113.100) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 04 Apr 2010 23:24:54 +0000 Received: (qmail 2881 invoked from network); 4 Apr 2010 23:24:52 -0000 Received: from unknown (HELO macbook-2.local) (stan@127.0.0.2) by mail.codesourcery.com with ESMTPA; 4 Apr 2010 23:24:52 -0000 Message-ID: <4BB91FBA.8090908@codesourcery.com> Date: Sun, 04 Apr 2010 23:25:00 -0000 From: Stan Shebs User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228) MIME-Version: 1.0 To: Eli Zaretskii CC: Stan Shebs , gdb-patches@sourceware.org Subject: Re: [PATCH] Infer $pc in a file's trace frame References: <4BB51AFC.1010303@codesourcery.com> <83tyruwd0a.fsf@gnu.org> In-Reply-To: <83tyruwd0a.fsf@gnu.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2010-04/txt/msg00067.txt.bz2 Eli Zaretskii wrote: > This is okay, but the last two sentences leave so much stuff > unexplained that I doubt the reader will be able to understand their > meaning, unless she is a tracepoint hacker. [...] It is a little obscure to explain, in fact it's a fundamental flaw of the tdump implementation that I didn't fully understand myself until recently. What I did for now was to whack those last two sentences, and add a couple more paragraphs in the tdump description. After writing them, my main thought is "what a lame design, can't we do tdump better?". :-) So perhaps after gdbserver tracepoints go in and more people get some familiarity, we should revisit both code and documentation. Stan