Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gdb-patches@sourceware.org
Cc: Stan Shebs <stan@codesourcery.com>
Subject: Re: [PATCH] Do partial xfers from trace file
Date: Tue, 13 Apr 2010 03:05:00 -0000	[thread overview]
Message-ID: <201004122304.39043.vapier@gentoo.org> (raw)
In-Reply-To: <4BBA5FE9.2060508@codesourcery.com>

[-- Attachment #1: Type: Text/Plain, Size: 1172 bytes --]

On Monday 05 April 2010 18:10:49 Stan Shebs wrote:
> Memory blocks in the trace buffer are limited to 65K (to save a couple
> bytes in the length field, since most blocks are small), and a tester
> trying to collect a quarter-megabyte(!) C++ object ran into trouble with
> that.  The fix is really a target-side thing, but the trace file reader
> needs to cognizant of this detail also.  Fortunately, we can exploit
> GDB's partial xfer mechanism, and just return what we find in one block,
> expecting that GDB will re-request the remainder.
> 
> I also made the tfile target has_all_memory, and added an emulation of
> QTro behavior, which lets disassembly and the like work, but rejects
> attempts to print non-constant globals that were not collected.
> Committed to trunk.

there's some problems with this commit ...

it introduces a warning which breaks with -Werror:
tracepoint.c: In function ‘tfile_xfer_partial’:
tracepoint.c:3895: error: ignoring return value of ‘read’, declared with 
attribute warn_unused_result

that particular piece of code also has slightly broken whitespace:
<space><space><tab><space><space>.......
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2010-04-13  3:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-05 22:11 Stan Shebs
2010-04-13  3:05 ` Mike Frysinger [this message]
2010-04-13  3:58   ` Stan Shebs
2010-04-13 16:27     ` Tom Tromey
2010-04-13 20:21       ` Mike Frysinger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201004122304.39043.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=gdb-patches@sourceware.org \
    --cc=stan@codesourcery.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox