From: Aleksandar Ristovski <aristovski@qnx.com>
To: Pierre Muller <muller@ics.u-strasbg.fr>
Cc: gdb@sourceware.org
Subject: Re: [RFC] Skipping final cleanups in quit_target
Date: Thu, 06 Mar 2008 16:51:00 -0000 [thread overview]
Message-ID: <47D01FAA.5020508@qnx.com> (raw)
In-Reply-To: <000001c87fa7$d40c48e0$7c24daa0$@u-strasbg.fr>
Pierre Muller wrote:
> This should at least be configurable
> because it is good practice to have
> program that do cleanups...
>
> An example is that you might want to
> check if gdb is leaking memory, and you
> can do that by simply looking at
> heap allocations remaining at exit.
> Such tests will be harder with your suggestions,
> which is the reason why I would suggest
> to make this a configurable option.
Yes, I am not against final cleanups in general, I am just looking for ways to
cut down the time users perceive as useless waiting.
>
> Pierre Muller
>
>> -----Original Message-----
>> From: gdb-owner@sourceware.org [mailto:gdb-owner@sourceware.org] On
>> Behalf Of Aleksandar Ristovski
>> Sent: Thursday, March 06, 2008 5:19 PM
>> To: gdb@sourceware.org
>> Subject: [RFC] Skipping final cleanups in quit_target
>>
>> Hello,
>>
>> Does anyone see a problem in skipping "do_final_cleanups
>> (ALL_CLEANUPS)" in
>> top.c (quit_target)?
>>
>> quit_target is called just before we exit gdb.
>>
>> I have a case where shutdown takes approx. 40sec. With skipping the
>> cleanups,
>> time is significantly shorter.
>>
>> Any thoughts?
>>
>> Thank you,
>>
>> Aleksandar Ristovski
>> QNX Software Systems
>
>
>
next prev parent reply other threads:[~2008-03-06 16:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 16:24 Aleksandar Ristovski
2008-03-06 16:34 ` Daniel Jacobowitz
2008-03-06 16:34 ` Aleksandar Ristovski
2008-03-06 16:45 ` Daniel Jacobowitz
2008-03-06 16:53 ` Aleksandar Ristovski
2008-03-06 16:40 ` Pierre Muller
2008-03-06 16:51 ` Aleksandar Ristovski [this message]
2008-03-07 3:17 ` Michael Snyder
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=47D01FAA.5020508@qnx.com \
--to=aristovski@qnx.com \
--cc=gdb@sourceware.org \
--cc=muller@ics.u-strasbg.fr \
/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