• 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: Odd crash/method call duplication?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Odd crash/method call duplication?


  • Subject: Re: Odd crash/method call duplication?
  • From: Lloyd Sargent <email@hidden>
  • Date: Wed, 12 Sep 2001 19:27:43 -0500

On Wednesday, September 12, 2001, at 05:29 PM, Nick Morris wrote:

As soon as the first { is passed the reading changes to:

# Frame
0 - [fileController parseFile:]
1 - [fileController parseFile:]

Why does [fileController setParser] get replaced with [fileController parseFile:]?

Curious...

I assume this is causing the problem?

Hmmm... not the cause, but perhaps a symptom...

If I comment out the whole contents of the method and just put in some code such as:

NSString *testString = @"this is a test";

NSLog(@"The method fired and %@", testString);

I get:

# Frame
0 - [fileController setParser]
1 - [fileController parseFile:]

And the method fires and exits OK.

As one would expect.

I have found that if I comment out sections of the code things also run fine (except the files don't get fully processed). It seems that it is the size/length of the method (which is quite long, around 350 lines of code) is the problem. Could it be?

Any thoughts, comments will be greatly appreciated!

My thoughts, take them what their worth <grin>.

First thing I would ask is how big are these files? If they are huge you might have some thrashing going on (memory is getting swapped and such).

However, my FIRST thought is that perhaps you are using something that is a) uninitialized, b) gets mangled c) gets overwritten. That is usually my first thought with typical C programs.

Next, for a sanity check, I would do a clean and rebuild (you didn't mention if you did this) prior to debugging. I have seen queer things happen when you THINK you have current code and for reasons only known by the IDE they aren't.

I guess the line that disturbs me the most is "crashes ranged from miss-matched objects and memory allocation problems" - yow! what the heck are you doing?!?!

In other words, I still don't have enough clues to give you even a WAG...

Sorry,

Cheers,

Lloyd
--------
Canna Software Development
"No llamas were served gin and tonics in the creation of this e-mail."


References: 
 >Odd crash/method call duplication? (From: Nick Morris <email@hidden>)

  • Prev by Date: Naming conventions
  • Next by Date: Re: Odd crash/method call duplication?
  • Previous by thread: Odd crash/method call duplication?
  • Next by thread: Re: Odd crash/method call duplication?
  • Index(es):
    • Date
    • Thread