Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: fche@redhat.com (Frank Ch. Eigler)
Cc: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [RFA/commit/dwarf] Create partial symbols for nested 	subprograms
Date: Fri, 12 Sep 2008 20:31:00 -0000	[thread overview]
Message-ID: <m3sks5w1j7.fsf@fleche.redhat.com> (raw)
In-Reply-To: <y0my71xmcku.fsf@ton.toronto.redhat.com> (Frank Ch. Eigler's message of "Fri\, 12 Sep 2008 14\:41\:21 -0400")

Joel> the one thing that I am wondering is how users will respond to an
Joel> unexpectedly long delay when entering a command that is usually fast
Joel> and yet takes a noticeably long time that one time. [...]

Frank> Could gdb use something like alarm(2) to issue progress notifications?

One open question with this patch is what to do about notifications.
There are two things to consider.

One problem is that gdb prints "(no debugging symbols found)" when
reading partial symbols.  With lazy loading, this is always printed,
even though it is not correct.  In my patch I removed this code.  This
is not really satisfying, at least if we assume that people want and
pay attention to these messages (I certainly have on occasion).

The other problem is whether to print something when reading partial
symbols.  This is a problem because it might print any time,
potentially messing up other output.

I'm not sure how this affects MI.

Tom


      reply	other threads:[~2008-09-12 20:31 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-10 20:20 Joel Brobecker
2008-09-10 20:35 ` Daniel Jacobowitz
2008-09-10 21:38   ` Tom Tromey
2008-09-11  5:01     ` Joel Brobecker
2008-09-11 22:15       ` Tom Tromey
2008-09-11 22:28         ` Daniel Jacobowitz
2008-09-11 22:33           ` Tom Tromey
2008-09-12  4:19           ` Joel Brobecker
2008-09-11 17:55   ` Joel Brobecker
2008-09-11 18:38     ` Daniel Jacobowitz
2008-09-11 21:53       ` Joel Brobecker
2008-09-13 15:14         ` Daniel Jacobowitz
2008-09-13 22:21           ` Joel Brobecker
2008-09-11 22:44       ` Tom Tromey
2008-09-12  4:18         ` Joel Brobecker
2008-09-12 16:51           ` Tom Tromey
2008-09-12 16:56             ` Joel Brobecker
2008-09-12 17:19               ` Tom Tromey
2008-09-12 17:43                 ` Joel Brobecker
2008-09-12 18:08                   ` Tom Tromey
2008-09-12 18:43                   ` Frank Ch. Eigler
2008-09-12 20:31                     ` Tom Tromey [this message]

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=m3sks5w1j7.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=fche@redhat.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