• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Clicking on a disabled ComboBox / FwUp: Window-closing sequence...
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Clicking on a disabled ComboBox / FwUp: Window-closing sequence...


  • Subject: Re: Clicking on a disabled ComboBox / FwUp: Window-closing sequence...
  • From: "Erik M. Buck" <email@hidden>
  • Date: Wed, 30 Jan 2002 11:30:09 -0600
  • Organization: EMB & Assocites Inc.

> A "bad access" message appears and, if one is using gdb, the stack
> frame area remains empty for, say, ten seconds or more; then, it
> fills up with a very large list, more than 500 items, where no one
> seems to refer to an application-specific method. I'm not so precise
> here, since I'm just asking whether my story is a well-known one.
>

You are describing infinite recursion. Look for a repeating pattern in the
gdb stack trace. Put a break point at a strategic point in the repeating
pattern of calls. Re-run and find out how the recursion started. Then
don't do that.


References: 
 >Clicking on a disabled ComboBox / FwUp: Window-closing sequence... (From: Andrea Perego <email@hidden>)

  • Prev by Date: Re: Simple Network Client Design (newbie alert)
  • Next by Date: Re: Control tints
  • Previous by thread: Clicking on a disabled ComboBox / FwUp: Window-closing sequence...
  • Next by thread: Fwd: NSDictionary -> Sparse Matrixes for Game Worlds)
  • Index(es):
    • Date
    • Thread