From: Tom Tromey <tromey@redhat.com>
To: Sterling Augustine <saugustine@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [Patch] More responsive QUITs
Date: Fri, 15 Jul 2011 20:49:00 -0000 [thread overview]
Message-ID: <m3wrfj9sr2.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CAEG7qUyG6S3pFiXsC2uyiPm8-WSexXBF64Gy+ARnF-wb30uKEA@mail.gmail.com> (Sterling Augustine's message of "Tue, 12 Jul 2011 15:51:29 -0700")
>>>>> "Sterling" == Sterling Augustine <saugustine@google.com> writes:
Sterling> Enclosed is a patch that adds calls to QUIT in various places which
Sterling> makes GDB more responsive to CTRL-C. In particular, reading a symbol
Sterling> file at start up can now be interrupted (although perhaps still not as
Sterling> responsive as one might like), as well as various other long running
Sterling> operations. I know at least two GDB developers have one or another of
Sterling> these on their TODO lists.
Yeah, I'm one of those.
Sterling> All three of these calls to QUIT have relatively close cleanup
Sterling> handlers:
[...]
I agree these are safe as to their immediate surrounds; but the problem
is what happens later on. That is, I think a quit when building
psymtabs will just leave the remaining psymtabs unread. This will
greatly interfere with debugging.
We have lazy psymtab reading now. So, it is tempting to try to record
where the processing was stopped and then restart it there. However,
this may be difficult to do without leaking memory, due to the use of
obstacks. Perhaps some leakage would be ok, though; or maybe by making
the granularity a single psymtab it would be possible not to leak at all
(not sure).
Tom
next prev parent reply other threads:[~2011-07-15 20:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 3:03 Sterling Augustine
2011-07-15 20:49 ` Tom Tromey [this message]
2011-07-20 18:46 ` Sterling Augustine
2011-07-22 1:14 ` Tom Tromey
[not found] ` <CAEG7qUxKevmBX=oCXr2p+x-zi-ZbBGLf3Gmb-X2bnVBpf7VKGA@mail.gmail.com>
[not found] ` <m3wrf6qeii.fsf@fleche.redhat.com>
2011-07-25 21:07 ` Sterling Augustine
2011-07-25 21:41 ` Tom Tromey
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=m3wrfj9sr2.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=saugustine@google.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