From: Gary Benson <gbenson@redhat.com>
To: Doug Evans <dje@google.com>
Cc: Michael Eager <eager@eagerm.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
binutils <binutils@sourceware.org>
Subject: Re: [PATCH] Support gzip compressed exec and core files in gdb
Date: Wed, 11 Mar 2015 18:32:00 -0000 [thread overview]
Message-ID: <20150311182111.GA5717@blade.nx> (raw)
In-Reply-To: <CADPb22T8A4p6Mj2sWVrk3OCROiwrdMBR+tXk45xdHPEMs5PLRg@mail.gmail.com>
Doug Evans wrote:
> On Wed, Mar 11, 2015 at 10:42 AM, Gary Benson <gbenson@redhat.com> wrote:
> > Michael Eager wrote:
> > > On 03/11/15 03:07, Gary Benson wrote:
> > > >Michael Eager wrote:
> > > > > Add support to automatically unzip compressed executable and
> > > > > core files. Files will be uncompressed into temporary
> > > > > directory (/tmp or $TMPDIR) and are deleted when GDB exits.
> > > > > This should be transparent to users, except for disk space
> > > > > requirements. The name of the uncompressed file is
> > > > > mentioned, but all references to the file in GDB messages is
> > > > > to the file which the user specified.
> > > >...
> > > > > diff --git a/gdb/common/filestuff.c b/gdb/common/filestuff.c
> > > > > index 14d6324..b2c31fd 100644
> > > > > --- a/gdb/common/filestuff.c
> > > > > +++ b/gdb/common/filestuff.c
> > > >...
> > > > > +#ifndef GDBSERVER
> > > >
> > > > Please do not add GDBSERVER conditionals to gdb/common, I spent
> > > > half a year removing them all.
> > > >
> > > > It looks like this code is only used by GDB, not gdbserver, so
> > > > the fix is simple, just put the code somewhere GDB-specific.
> > >
> > > Sure. Any suggestions? gdb_bfd.c seems like the wrong place.
> >
> > gdb/utils.c maybe?
>
> Fine by me.
> Though, OTOH, there's nothing intrinsic in what's being done there
> that gdbserver (or anything else that might want to use common)
> couldn't use it tomorrow.
> I'd be ok with common/compression.c or some such.
Do we really want to be putting things in common speculatively?
Cheers,
Gary
--
http://gbenson.net/
next prev parent reply other threads:[~2015-03-11 18:32 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 23:01 Michael Eager
2015-03-11 2:37 ` Mike Frysinger
2015-03-11 15:00 ` Michael Eager
2015-03-11 8:15 ` Alan Modra
2015-03-11 14:57 ` Michael Eager
2015-03-12 0:08 ` Alan Modra
2015-03-12 0:45 ` Michael Eager
2015-03-12 2:51 ` Alan Modra
2015-03-12 16:14 ` Michael Eager
2015-03-13 0:13 ` Alan Modra
2015-03-11 10:07 ` Gary Benson
2015-03-11 14:58 ` Michael Eager
2015-03-11 17:42 ` Gary Benson
2015-03-11 18:10 ` Doug Evans
2015-03-11 18:32 ` Gary Benson [this message]
2015-03-11 18:56 ` Doug Evans
2015-03-11 16:15 ` Eli Zaretskii
2015-03-11 19:55 ` Michael Eager
2015-03-11 20:18 ` Mike Frysinger
2015-03-11 20:24 ` Eli Zaretskii
2015-03-12 21:17 ` Sergio Durigan Junior
2015-03-13 6:04 ` Eli Zaretskii
2015-03-11 18:24 ` Cary Coutant
2015-03-11 20:12 ` Michael Eager
2015-03-11 20:19 ` Doug Evans
2015-03-11 22:13 ` Jan Kratochvil
2015-03-11 23:14 ` Doug Evans
2015-03-12 11:32 ` Jan Kratochvil
2015-03-12 15:24 ` Michael Eager
2015-03-12 0:40 ` Michael Eager
2015-03-12 11:31 ` Pedro Alves
2015-03-12 15:34 ` Michael Eager
2015-03-12 16:13 ` Pedro Alves
2015-03-12 16:58 ` Michael Eager
2015-03-12 17:11 ` Jan Kratochvil
2015-03-12 17:37 ` Michael Eager
2015-03-12 17:48 ` Jan Kratochvil
2015-03-13 6:25 ` Ed Maste
2015-03-19 0:58 ` Michael Eager
2015-03-19 3:45 ` Eli Zaretskii
2015-03-20 22:16 ` Mike Frysinger
2015-03-27 15:26 ` Michael Eager
2015-03-28 4:49 ` Mike Frysinger
2015-03-28 16:56 ` Michael Eager
2015-04-01 12:41 ` Pedro Alves
2015-04-01 18:52 ` Michael Eager
2015-04-01 19:10 ` Pedro Alves
2015-05-01 14:40 ` Michael Eager
2015-05-01 17:53 ` Eli Zaretskii
2015-05-01 22:03 ` Michael Eager
2015-05-04 7:50 ` Mike Frysinger
2015-06-15 15:14 ` Michael Eager
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=20150311182111.GA5717@blade.nx \
--to=gbenson@redhat.com \
--cc=binutils@sourceware.org \
--cc=dje@google.com \
--cc=eager@eagerm.com \
--cc=gdb-patches@sourceware.org \
/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