From: Doug Evans <xdje42@gmail.com>
To: Simon Marchi <simon.marchi@ericsson.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH 00/21] struct symtab split part 2
Date: Fri, 14 Nov 2014 17:19:00 -0000 [thread overview]
Message-ID: <CAP9bCMT15_2GT2hR_NqmbKFgMcKKMCxevwwObiEkVVZ_cPWXtQ@mail.gmail.com> (raw)
In-Reply-To: <5464D8A2.9020004@ericsson.com>
On Thu, Nov 13, 2014 at 8:13 AM, Simon Marchi <simon.marchi@ericsson.com> wrote:
>[...]
> As someone who never quite understood who the symtab mechanism worked in gdb,
> I welcome this change very much It makes the data structure a bit more
> self-descriptive, which in turn helps understanding the algorithms used.
Agreed.
> That lovely ascii art chart makes things very clear, and I would even suggest
> including it somewhere in the code (symtab.h I guess).
Good idea, will do.
> Thanks a lot for your work.
Thanks.
next prev parent reply other threads:[~2014-11-14 17:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 12:49 Doug Evans
2014-11-13 16:13 ` Simon Marchi
2014-11-14 17:19 ` Doug Evans [this message]
2014-11-16 5:34 ` Doug Evans
2014-11-18 9:06 ` Doug Evans
2014-11-18 15:38 ` Pedro Alves
2014-11-20 15:51 ` Doug Evans
2014-11-23 19:22 ` Doug Evans
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=CAP9bCMT15_2GT2hR_NqmbKFgMcKKMCxevwwObiEkVVZ_cPWXtQ@mail.gmail.com \
--to=xdje42@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@ericsson.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