Re: - (IBAction) executes normally, but then crushes.
Re: - (IBAction) executes normally, but then crushes.
- Subject: Re: - (IBAction) executes normally, but then crushes.
- From: mm w <email@hidden>
- Date: Thu, 19 Mar 2009 16:03:08 -0700
There is no manual except a descent knoledge of assembly when you program
You are trying to write at freed address
On 3/19/09, Тимофей Даньшин <email@hidden> wrote:
> Hello again.
>
> Here is what is says in the debugger:
>
> 0 objc_msgSend
> 1 NSPopAutoReleasePool
> 2 -[NSApplication run]
> 3 NSApplicationMain
> 4 main
>
> Here is the stacktrace with the 0th line selected.
>
>
> 0x91edd670 <+0000> mov 0x8(%esp),ìx
> 0x91edd674 <+0004> mov 0x4(%esp),êx
> 0x91edd678 <+0008> cmp $0xfffeb010,ìx
> 0x91edd67e <+0014> je 0x91edd6fb <objc_msgSend+139>
> 0x91edd680 <+0016> test êx,êx
> 0x91edd682 <+0018> je 0x91edd6e0 <objc_msgSend+112>
> 0x91edd684 <+0020> mov 0x0(êx),íx
> 0x91edd687 <+0023> push íi
> >>> 0x91edd688 <+0024> mov 0x20(íx),íi // The line with the
> red arrow
> 0x91edd68b <+0027> push %esi
> 0x91edd68c <+0028> mov 0x0(íi),%esi
> 0x91edd68f <+0031> lea 0x8(íi),íi
> 0x91edd692 <+0034> mov ìx,íx
> 0x91edd694 <+0036> shr $0x2,íx
> 0x91edd697 <+0039> and %esi,íx
> 0x91edd699 <+0041> mov (íi,íx,4),êx
>
> By the way, are there any manuals on reading these stacktraces?
>
>
> On Mar 20, 2009, at 1:36 AM, Shawn Erickson wrote:
>
>> 2009/3/19 Тимофей Даньшин <email@hidden>:
>>
>>> 2009-03-19 23:47:28.204 Untitled[16510:10b] The splitString is 'dra'
>>>
>>> [Session started at 2009-03-19 23:47:28 +0300.]
>>> 2009-03-19 23:47:28.207 Untitled[16510:10b] The splitString is 'raw'
>>> 2009-03-19 23:47:28.211 Untitled[16510:10b] The splitString is 'aw.'
>>> 2009-03-19 23:47:28.214 Untitled[16510:10b] Finished Adding to DB;
>>> Loading program into debugger...
>>> GNU gdb 6.3.50-20050815 (Apple version gdb-962) (Sat Jul 26
>>> 08:14:40 UTC
>>> 2008)
>>>
>>> What can possibly go wrong there?
>>
>> Can you outline how it crashed? The backtrace for the thread that
>> crashed, the type of crash, etc.
>>
>> If you use the debugger you should be able to tell the code pathway
>> involved in the crash... (likely best to launch the application in the
>> debugger and then cause the failure you are seeing).
>>
>> -Shawn
>
> _______________________________________________
>
> Cocoa-dev mailing list (email@hidden)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
>
--
-mmw
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden