From: Weimin Pan <weimin.pan@oracle.com>
To: Simon Marchi <simark@simark.ca>, gdb-patches@sourceware.org
Subject: Re: [PATCH v3] gdb: CTF support
Date: Fri, 04 Oct 2019 21:29:00 -0000 [thread overview]
Message-ID: <cb859f85-d15c-36b5-8bb5-839bb077d7d1@oracle.com> (raw)
In-Reply-To: <31e9cadf-29b3-be60-77ce-eb856fe82c38@simark.ca>
On 10/3/2019 6:10 PM, Simon Marchi wrote:
> On 2019-10-03 6:56 p.m., Weimin Pan wrote:
>> [Changes from v2:
>>Â - Address Simon Marchi's comments, mainly:
>>Â Â Â * Use gdb::unique_xmalloc_ptr<> to minimize the manual memory
management.
>>Â Â Â * Modify create_partial_symtab to handle multiple-CUs correctly.
>>Â Â Â * Improve defining/using ctf_context_t and field_info structs.
>>Â Â Â * Conform to GNU's coding standards.
>>
>> ....
>> This patch has missing features and limitations which we will add and
>> address in the future patches.
>
> Hi Weimin,
>
> 1. Could you please split the renaming of ctf (the trace format) to
tracectf to its
> own patch, just before this patch (send them as a patch series)? It
will keep this
> patch more focused on its main topic.
Hi Siomn,
FYI, just posted the patch series.
>
> 2. When applying the patch, git told me:
>
> .git/rebase-apply/patch:1079: trailing whitespace.
>Â Â Â Â Â Â {
> .git/rebase-apply/patch:1083: trailing whitespace.
>Â Â Â Â Â Â }
> .git/rebase-apply/patch:1824: trailing whitespace.
>
> .git/rebase-apply/patch:1889: trailing whitespace.
>
> .git/rebase-apply/patch:1894: trailing whitespace.
>
> Can you try to fix those? One way of finding the offenders is to do
"git show"
> and look for trailing spaces by searching for `. $` in less.
Fixed.
>
> 3. I think the binutils patchset has been merged now? Could you
please rebase
> on the latest master and force-push your users/weimin/ctf branch?
Yes, binutils has been pushed yesterday. Would you please take a look at
the patch series and let me know if you have any comments.
>
>> gdb/ChangeLog
>> +2019-10-03 Weimin Pan <weimin.pan@oracle.com>
>> +
>> +Â Â Â * gdb/ctfread.c: New file.
>> +Â Â Â * gdb/ctfread.h: New file.
>> +Â Â Â * gdb/elfread.c: Include ctfread.h.
>> +Â Â Â (struct elfinfo text_p): New member ctfsect.
>> +Â Â Â (elf_locate_sections): Mark CTF section.
>> +Â Â Â (elf_symfile_read): Call elfctf_build_psymtabs.
>> +Â Â Â * gdb/Makefile.in (LIBCTF): Add.
>> +Â Â Â (CLIBS): Use it.
>> +Â Â Â (CDEPS): Likewise.
>> +Â Â Â (DIST): Add ctfread.c.
>> +Â Â Â * gdb/tracectf.h: Rename, was gdb/ctf.h
>> +Â Â Â * gdb/ctf.c: Replace ctf.h with tracectf.h
>> +Â Â Â * gdb/tracefile.c: Likewise
>> +Â Â Â * gdb/tracepoint.c: Remove unused include ctf.h
>> +Â Â Â * gdb/mi/mi-main.c: Likewise
>
> Drop all the gdb/ prefixes from this list, as we want all entries to
be relative
> to the ChangeLog file they appear in.
Done.
>
>> +Â Â Â * Makefile.def (dependencies): Add all-libctf to all-gdb
>> +Â Â Â * Makefile.in: Add "all-gdb: maybe-all-libctf"
>
> Changes made to the top-level Makefile.def/Makefile.in will go in the
top-level
> ChangeLog.
>
> Simon
Thanks,
Weimin
next prev parent reply other threads:[~2019-10-04 21:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-03 22:58 Weimin Pan
2019-10-04 1:11 ` Simon Marchi
2019-10-04 21:29 ` Weimin Pan [this message]
2019-10-07 9:33 ` Tom de Vries
2019-10-07 9:44 ` Tom de Vries
2019-10-07 12:07 ` Andrew Burgess
2019-10-07 14:58 ` Simon Marchi
2019-10-07 16:08 ` Wei-min Pan
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=cb859f85-d15c-36b5-8bb5-839bb077d7d1@oracle.com \
--to=weimin.pan@oracle.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
/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