public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: Andrew Burgess <andrew.burgess@embecosm.com>, gdb-patches@sourceware.org
Subject: Re: [PATCHv2 0/5] "info sources" - group by objfile
Date: Thu, 3 Jun 2021 09:15:57 -0400	[thread overview]
Message-ID: <6fa16c3f-aab1-7436-1e15-cfa94be506ed@polymtl.ca> (raw)
In-Reply-To: <20210603092752.GN2672@embecosm.com>

On 2021-06-03 5:27 a.m., Andrew Burgess wrote:> Any thoughts on the new approach?  Specifically, changing the
> behaviour of CLI 'info sources'?

I already gave my opinion, so I guess you are not waiting for my to
state it again.

But I noticed a little something, here's an excerpt:

    /usr/lib/liblzma.so.5:

    /usr/lib/libbabeltrace.so.1:

    /usr/lib/libbabeltrace-ctf.so.1:

    /usr/lib/libipt.so.2:
    (Full debug information has not yet been read  for this file.)

    /usr/src/debug/libipt-git/libipt/internal/include/pt_section.h, /usr/include/bits/fcntl2.h, /usr/include/sys/stat.h, /usr/include/bits/string_fortified.h, 
    /usr/src/debug/libipt-git/libipt/src/posix/pt_section_posix.c, /usr/include/bits/stdio2.h, /usr/src/debug/libipt-git/include/posix/threads.h, 
    /usr/src/debug/libipt-git/libipt/src/pt_section_file.c, /usr/src/debug/libipt-git/libipt/src/pt_section.c, /usr/src/debug/libipt-git/libipt/internal/include/pt_mapped_section.h, 
    /usr/src/debug/libipt-git/libipt/src/pt_msec_cache.c, /usr/src/debug/libipt-git/libipt/src/pt_block_cache.c, /usr/src/debug/libipt-git/libipt/include/intel-pt.h, 
    /usr/src/debug/libipt-git/libipt/internal/include/pt_block_cache.h, /usr/src/debug/libipt-git/libipt/src/pt_block_decoder.c, /usr/src/debug/libipt-git/libipt/src/pt_insn.c, 
    /usr/src/debug/libipt-git/libipt/src/pt_config.c, /usr/src/debug/libipt-git/libipt/src/pt_decoder_function.c, /usr/src/debug/libipt-git/libipt/src/pt_packet.c, 
    /usr/src/debug/libipt-git/libipt/src/pt_event_queue.c, /usr/src/debug/libipt-git/libipt/src/pt_asid.c, /usr/src/debug/libipt-git/libipt/src/pt_time.c, 
    /usr/src/debug/libipt-git/libipt/src/pt_insn_decoder.c, /usr/src/debug/libipt-git/libipt/src/pt_retstack.c, /usr/src/debug/libipt-git/libipt/src/pt_image_section_cache.c, 
    /usr/src/debug/libipt-git/libipt/src/pt_image.c, /usr/src/debug/libipt-git/libipt/internal/include/pt_ild.h, /usr/src/debug/libipt-git/libipt/src/pt_ild.c, 
    /usr/src/debug/libipt-git/libipt/src/pt_tnt_cache.c, /usr/src/debug/libipt-git/libipt/src/pt_last_ip.c, /usr/src/debug/libipt-git/libipt/src/pt_version.c, 
    /usr/src/debug/libipt-git/libipt/src/pt_sync.c, /usr/src/debug/libipt-git/libipt/src/pt_encoder.c, /usr/src/debug/libipt-git/libipt/src/pt_query_decoder.c, 
    /usr/src/debug/libipt-git/libipt/src/pt_packet_decoder.c, /usr/src/debug/libipt-git/libipt/src/pt_error.c

    /usr/lib/libmpfr.so.6:

Objfiles that have debug info, but not completely read-in, have this
"Full debug information has not yet been read for this file" notice.
But objfiles that have no debug info say nothing.  Should they maybe say
"No debug information available for this file"?

Simon

  reply	other threads:[~2021-06-03 13:16 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-26 17:06 [PATCH 0/4] New option for 'info sources', also better MI support Andrew Burgess
2021-04-26 17:07 ` [PATCH 1/4] gdb: add new function quick_symbol_functions::has_unexpanded_symbols Andrew Burgess
2021-05-13 14:38   ` Simon Marchi
2021-05-13 17:29     ` Tom Tromey
2021-05-13 14:46   ` Simon Marchi
2021-04-26 17:07 ` [PATCH 2/4] gdb: make struct output_source_filename_data more C++ like Andrew Burgess
2021-05-13 14:58   ` Simon Marchi
2021-04-26 17:07 ` [PATCH 3/4] gdb: add new -group-by-binary flag to info sources command Andrew Burgess
2021-04-26 17:34   ` Eli Zaretskii
2021-05-13 15:05   ` Simon Marchi
2021-05-15  8:45     ` Andrew Burgess
2021-05-15 13:19       ` Simon Marchi
2021-04-26 17:07 ` [PATCH 4/4] gdb/mi: extend -file-list-exec-source-files command Andrew Burgess
2021-04-26 17:39   ` Eli Zaretskii
2021-05-13 15:47   ` Simon Marchi
2021-05-13 10:34 ` [PATCH 0/4] New option for 'info sources', also better MI support Andrew Burgess
2021-05-19 11:12 ` [PATCHv2 0/5] "info sources" - group by objfile Andrew Burgess
2021-05-19 11:12   ` [PATCHv2 1/5] gdb: add new function quick_symbol_functions::has_unexpanded_symbols Andrew Burgess
2021-05-19 11:12   ` [PATCHv2 2/5] gdb: make struct output_source_filename_data more C++ like Andrew Burgess
2021-05-19 11:12   ` [PATCHv2 3/5] gdb/mi: add regexp filtering to -file-list-exec-source-files Andrew Burgess
2021-05-19 11:51     ` Eli Zaretskii
2021-05-19 11:12   ` [PATCHv2 4/5] gdb/mi: add new --group-by-objfile flag for -file-list-exec-source-files Andrew Burgess
2021-05-19 11:44     ` Eli Zaretskii
2021-05-19 11:12   ` [PATCHv2 5/5] gdb: change info sources to group results by objfile Andrew Burgess
2021-05-19 11:53     ` Eli Zaretskii
2021-06-03 13:08     ` Simon Marchi
2021-06-03  9:27   ` [PATCHv2 0/5] "info sources" - group " Andrew Burgess
2021-06-03 13:15     ` Simon Marchi [this message]
2021-06-07 18:32   ` [PATCHv3 " Andrew Burgess
2021-06-07 18:32     ` [PATCHv3 1/5] gdb: add new function quick_symbol_functions::has_unexpanded_symbols Andrew Burgess
2021-06-07 18:32     ` [PATCHv3 2/5] gdb: make struct output_source_filename_data more C++ like Andrew Burgess
2021-07-05 12:31       ` Tom de Vries
2021-07-26 13:21         ` Andrew Burgess
2021-06-07 18:32     ` [PATCHv3 3/5] gdb/mi: add regexp filtering to -file-list-exec-source-files Andrew Burgess
2021-06-07 18:32     ` [PATCHv3 4/5] gdb/mi: add new --group-by-objfile flag for -file-list-exec-source-files Andrew Burgess
2021-06-07 18:32     ` [PATCHv3 5/5] gdb: change info sources to group results by objfile Andrew Burgess
2021-06-21 12:02     ` PING! Re: [PATCHv3 0/5] "info sources" - group " Andrew Burgess
2021-06-25 20:08       ` Andrew Burgess

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=6fa16c3f-aab1-7436-1e15-cfa94be506ed@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=andrew.burgess@embecosm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).