public inbox for archer@sourceware.org
 help / color / mirror / Atom feed
From: Phil Muldoon <pmuldoon@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Project Archer <archer@sourceware.org>
Subject: Re: [Archer] [patch] PR python/10344
Date: Wed, 23 Sep 2009 16:17:00 -0000	[thread overview]
Message-ID: <4ABA49D2.7030802@redhat.com> (raw)
In-Reply-To: <20090923154442.GP7961@adacore.com>

On 09/23/2009 04:44 PM, Joel Brobecker wrote:
>> The only thing I can think to do in this case is just to add one more
>> level to the maximum uiout levels. I am not sure why the initial level
>> is set at such a small level. The uiout level struct is not particularly
>> large. Anyway, what do you think? This fixes the PR.
>>      
> The only thing I can think of is protecting ourselves against reaching
> the maximum number of open file descriptors? Perhaps it's ridiculously
> low on certain systems? I'd have a hard time believing that raising
> MAX_UI_OUT_LEVELS from 6 to 7 would make any difference so I would be
> inclined to give it a try.  I looked at the history of this constant,
> and it was initially defined as 5, and then raised to 6 without much
> comment in order to fix PR cli/654.
>
> I forgot how to convert old PR numbers into the new ones (I need to
> write this down in my tips-and-tricks file). Anyone remembers?
>
>    

http://sourceware.org/bugzilla/show_bug.cgi?id=7759

But yeah, not much in there other than what was on the list. I think, it 
had some vague to do with hurd from reading around the gmane archives.

There are other cases where the limit was exceeded but these exclusively 
refer to bugs with cleanups.

Regards

Phil

  reply	other threads:[~2009-09-23 16:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-23 12:33 Phil Muldoon
2009-09-23 15:45 ` [Archer] " Joel Brobecker
2009-09-23 16:17   ` Phil Muldoon [this message]
2009-09-25 18: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=4ABA49D2.7030802@redhat.com \
    --to=pmuldoon@redhat.com \
    --cc=archer@sourceware.org \
    --cc=brobecker@adacore.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).