• 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: GDB crashing
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GDB crashing


  • Subject: Re: GDB crashing
  • From: Laurence Harris <email@hidden>
  • Date: Sun, 15 Apr 2007 02:01:33 -0400


On Apr 15, 2007, at 12:13 AM, Ed Martin wrote:

Hi, I'm not sure what i should do about this, GDB keeps crashing on my code while i try and debug my application in Xcode, i know that i have bad code, its basically that I'm new to carbon and I'm messing the pointers up or something,

Pointers are not unique to Carbon. What do you mean by "bad code?" Do you know what's bad or do you just believe the code as a problem that's causing this or other issues?


anyways my code is making gdb crash so i though i should tell someone, should i file a bug report with Apple?

this is what i get with GDB

(gdb) continue
/SourceCache/gdb/gdb-573/src/gdb/frame.c:635: internal-error: frame_register: Assertion `frame != NULL && frame->next != NULL' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.


The Debugger has exited with status 1.The Debugger has exited with status 1.
Timed out fetching data. Variable display may be inaccurate.
(gdb)


the actual line in my source code is the property >= kColFirst, the crash happens when i click "Step Over" and the application goes to this line

        if (property >= kColFirst){

this is happening inside an Item-data callback for the DataBrowser

BTW, my version of GDB is

GNU gdb 6.3.50-20050815 (Apple version gdb-573) (Fri Oct 20 15:50:43 GMT 2006)

and if anyone needs more source to my application i can give it to you (its just a school project), but be warned, I'm new to Carbon and i know I'm doing at least a few obvious things the wrong way

Well, my first thought is that you should fix anything you know needs to be fixed or rewritten because the problem you describe has the earmarks of memory corruption. And if you want someone to take a look at it, it should be written so someone can read and understand it easily. In other words, it should be the best you know how to do before asking someone to look at it. Is that the case currently?


Larry
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >GDB crashing (From: Ed Martin <email@hidden>)

  • Prev by Date: Re: Applescripting Xcode font sizes
  • Next by Date: Re: GDB crashing
  • Previous by thread: GDB crashing
  • Next by thread: Re: GDB crashing
  • Index(es):
    • Date
    • Thread