> On Jul 14, 2022, at 3:58 AM, Christopher Snowhill wrote:
>
> My app, Cog (https://cog.losno.co <https://cog.losno.co/> /
> https://github.com/losnoco/Cog <https://github.com/losnoco/Cog>) is hitting
> the stack size limit of 512 KiB on macOS. I am not even m
My app, Cog (https://cog.losno.co <https://cog.losno.co/> /
https://github.com/losnoco/Cog <https://github.com/losnoco/Cog>) is hitting the
stack size limit of 512 KiB on macOS. I am not even making heavy use of local
variables. I am, however, making a lot of Cocoa object
Hi,
On 4/20/18 10:15 AM, Glen Huang wrote:
I have an app where user can edit data and save to my server. I wonder what’s
the best
way to update affected view controllers in the navigation stack?
To give an example, imagine it’s an a recipe app where users can create recipes
and
edit other’s
er can edit data and save to my server. I wonder
>> what’s the best way to update affected view controllers in the navigation
>> stack?
>
> If I were to give a literal answer to your question, I'd suggest a callback
> method (either as a closure property on the child
> On Apr 20, 2018, at 1:15 AM, Glen Huang <hey...@gmail.com> wrote:
>
> I have an app where user can edit data and save to my server. I wonder what’s
> the best way to update affected view controllers in the navigation stack?
If I were to give a literal answer to your que
Hi,
I have an app where user can edit data and save to my server. I wonder what’s
the best way to update affected view controllers in the navigation stack?
To give an example, imagine it’s an a recipe app where users can create recipes
and edit other’s recipes. In the navigation controller’s
On Jul 7, 2017, at 03:08:19, Quincey Morris
wrote:
>
> You didn’t look into Jens’s first suggestion: “This.” In other words, keep
> the recursion but use more than one thread.
Which was referring to my suggestion. ;) (Just to make it easier for the OP to
On Jul 6, 2017, at 22:34 , Graham Cox wrote:
>
> So… unless someone has any bright ideas (or has even read this, very
> unlikely), I’ll ponder some more.
You didn’t look into Jens’s first suggestion: “This.” In other words, keep the
recursion but use more than one
> On 7 Jul 2017, at 2:44 am, Jens Alfke <j...@mooseyard.com> wrote:
>
>
>> On Jul 6, 2017, at 8:42 AM, Steve Mills <sjmi...@mac.com> wrote:
>>
>> Why can't you spawn your own thread to do the recursive code? Create the
>> NSThread, set its st
> On Jul 6, 2017, at 8:42 AM, Steve Mills <sjmi...@mac.com> wrote:
>
> Why can't you spawn your own thread to do the recursive code? Create the
> NSThread, set its stack size, light its fuse to do the processing, and delete
> it.
This. Although I would also consider
On 6 Jul 2017, at 16:33, Graham Cox <graham@bigpond.com> wrote:
>
> I appreciate your answer, and I realise there’s no API that could set the
> stack size after the thread is created.
>
> But presumably the stack size of the thread is set somewhere as a parameter
>
On Jul 6, 2017, at 10:33:56, Graham Cox <graham@bigpond.com> wrote:
>
>
> I appreciate your answer, and I realise there’s no API that could set the
> stack size after the thread is created.
>
> But presumably the stack size of the thread is set somewhere as a pa
> On 6 Jul 2017, at 11:04 pm, Alastair Houghton <alast...@alastairs-place.net>
> wrote:
>
> There’s no way an API could exist that did that - in general it’d have to
> copy the entire existing stack to a new location, then update a load of
> pointers that it ha
On 6 Jul 2017, at 06:57, Graham Cox <graham@bigpond.com> wrote:
>
> I’m wondering if there’s a way to increase the stack size of the thread that
> opens my NSDocument in the background.
There’s no way an API could exist that did that - in general it’d have to copy
the entire
Hi all,
I’m wondering if there’s a way to increase the stack size of the thread that
opens my NSDocument in the background.
NSThread has a -setStackSize: method which would work, but it must be set prior
to starting the thread. The problem is I don’t start the thread - Cocoa does.
By the time
On Sun, Dec 6, 2015, at 10:10 AM, Dave wrote:
> Hi,
>
> I’m not sure what to use for the Frame though?
It doesn't matter. Auto Layout will change the frame on the first layout
pass anyway.
--Kyle Sluder
> The way this is setup is
> that I have a Stack View an empty Stack View
You can just do [[NSStackView alloc] initwithFrame:]
> On Dec 6, 2015, at 6:23 AM, Dave <d...@looktowindward.com> wrote:
>
> Hi All,
>
> How do I create an Empty Stack View in code? The only method I can find that
> that creates a Stack View is stackViewWithView
Hi,
I’m not sure what to use for the Frame though? The way this is setup is that I
have a Stack View an empty Stack View in a NIB, as so:
@property (nonatomic,strong)IBOutlet NSStackView* pLabelMainRowStackView;
//Vertical
There is a then a Row Array which contains Column Arrays
Hi All,
How do I create an Empty Stack View in code? The only method I can find that
that creates a Stack View is stackViewWithViews and you can’t pass nil to this.
Do I have to pass an empty array or can I just do [[NSStackView alloc] init]; ?
All the Best
Dave
>>
>>
>>>
>>> Because there are 5 buttons in the top and bottom rows, and 3 in the
>>> vertical left and right rows, the spacing in the vertical stack views are
>>> not as “tight” as I want it to be.
>>>
>>> What I
- Original Message -
From: "Ken Thomases" <k...@codeweavers.com>
To: "Michael de Haan " <m...@comcast.net>
Cc: "Cocoa Developers" <Cocoa-dev@lists.apple.com>
Sent: Wednesday, November 11, 2015 4:59:51 PM
Subject: Re: Stack View Qu
sure I understand from your
pictures)?
I would expect that to work generically, but I don’t have any particular
insight into why it might not. If that fails, you might try doing 2 vertical
stacks and using baseline alignments across the vertical stack views
instead...
Thanks
.
To manage this layout I created four horizontal stack views, one for each
label-popup pair, and placed those four stack views into a vertical stack
view. At this point, the labels are all sized to fit, as are the popups.
If I add a constraint that says one label should be equal width to another
In my OS X view, I have four popup buttons vertically stacked, each with a
label on the left. The labels all have equal width as each other and are
right-aligned, and the popups all have equal width as well.
To manage this layout I created four horizontal stack views, one for each
label-popup
Keary,
You made me question what I thought I knew, so I went back and changed my
method returning the number of rows (views) to log its operation so I could
make sure it was returning 16 as it should. And of course I found it was
returning 0.
What I previously didn’t know is that the table
On 4 Oct 2014, at 02:06, Charles Jenkins cejw...@gmail.com wrote:
Okay, here’s a dumb question… How do you make a stack view actually stack
things? When I add subviews into a stack view, instead of appearing one after
another as I expect, they’re all laid on top of one another
On Oct 4, 2014, at 8:49 PM, Charles Jenkins cejw...@gmail.com wrote:
Keary, I see you’re right: NSTableViewDelegate’s tableView:heightOfRow: will
be key if my stack of editors appears in a table view. I’ve been struggling
all day to get a test program to call my delegate’s functions. I must
On Oct 3, 2014, at 8:27 PM, Charles Jenkins cejw...@gmail.com wrote:
What I’m trying to make is a scroll view containing a vertical stack of
editors for RTF subdocuments. Each of the text views should size itself to
fit the width of the scroll view, but grow vertically as much as necessary
On Oct 4, 2014, at 11:27 AM, Charles Jenkins cejw...@gmail.com wrote:
I just asked a question about the NSStackView, but perhaps I’m looking at the
wrong control altogether.
What I’m trying to make is a scroll view containing a vertical stack of
editors for RTF subdocuments. Each
Thank you for responding, guys.
Keary, I see you’re right: NSTableViewDelegate’s tableView:heightOfRow: will be
key if my stack of editors appears in a table view. I’ve been struggling all
day to get a test program to call my delegate’s functions. I must say, the
table view is a very
Okay, here’s a dumb question… How do you make a stack view actually stack
things? When I add subviews into a stack view, instead of appearing one after
another as I expect, they’re all laid on top of one another.
I created a sample program with one window filled with a scroll view, and
inside
I just asked a question about the NSStackView, but perhaps I’m looking at the
wrong control altogether.
What I’m trying to make is a scroll view containing a vertical stack of editors
for RTF subdocuments. Each of the text views should size itself to fit the
width of the scroll view
On 2014 Sep 28, at 22:06, Kyle Sluder k...@ksluder.com wrote:
Do you have a cycle in your nextResponder chain? Remember than
NSViewController now inserts itself into the responder chain on 10.10.
YES! That explains all of the forwardMethod() madness. My subclass of
NSViewController,
anywhere in a document window (that contains a tab view), the
blows its stack. See call stack below, prior to which I had clicked in the
title bar.
Any ideas or similar experiences, let us know. Possibly this is related to the
addition of NSTabViewController in 10.10.
Jerry Krinock
…
#130958
On Sep 28, 2014, at 9:48 PM, Jerry Krinock je...@ieee.org wrote:
…
#1309580x7fff96f9ad70 in forwardMethod ()
#1309590x7fff96f9ad70 in forwardMethod ()
#1309600x7fff974074ea in -[NSTabView mouseDown:] ()
Do you have a cycle in your nextResponder chain? Remember than
no? Or
simply setting enabled state of the back button to observe what the
UITextFieldDelegate returns?
Cheers.
On Jan 9, 2014, at 7:22 PM, Rick Mann wrote:
What's the right way to validate fields in an editable detail view in a
navigation stack? It seems that the API doesn't really provide
What's the right way to validate fields in an editable detail view in a
navigation stack? It seems that the API doesn't really provide a good means to
do so without a lot of contortions, and so I wonder what the intended behavior
is.
Here's what I've got: A UINavigationController stack
to validate fields in an editable detail view in a
navigation stack? It seems that the API doesn't really provide a good means
to do so without a lot of contortions, and so I wonder what the intended
behavior is.
Here's what I've got: A UINavigationController stack with a UITableView
iOS 6.1.3.
I have a navigation stack in a UIPopover, using autolayout, and I'm
programmtically instantiating a couple of view controllers from scenes in the
storyboard and installing them in a view controller container view in the view
controller on the top of my navigation stack. I swap VCs
have a navigation stack in a UIPopover, using autolayout, and I'm
programmtically instantiating a couple of view controllers from scenes in the
storyboard and installing them in a view controller container view in the
view controller on the top of my navigation stack. I swap VCs as the user
). In the
average case its stack size is O( log n ). I'm not dead certain but I
think the worst case stack size is O( n^2 ) as well.
Look through all your code for any methods that have many local
variables, any locals that are large, or very long methods. The
compiler puts invisible
I have a process that's generating a bunch of MIDI files. The process itself
runs okay, but if I request a large number of files and pause execution at some
point part way through, I notice that there are literally thousands of frames
on the stack. In some cases, it will crash before
Are you using any recursive algorithms?
You might be but not know it. For example the C standard library
qsort() is recursive. It's worst case runtime is O( n^2 ). In the
average case its stack size is O( log n ). I'm not dead certain but I
think the worst case stack size is O( n^2 ) as well
. So in
all likelihood I'm blowing the stack to smithereens!
cheers,
J.
On 2013-06-30, at 1:24 PM, Michael Crawford mdcrawf...@gmail.com wrote:
Are you using any recursive algorithms?
You might be but not know it. For example the C standard library
qsort() is recursive. It's worst case
On 21 Apr 2012, at 4:53 PM, The Rhythmic wrote:
Hi, Am a newbie to iOS programming. This is what am trying to do:
1. The user enters some text in the screen and it keeps getting added to a
UITableView.
2. As usual, it's getting added *from* the top.
3. But I want to add it from the
Hi, Am a newbie to iOS programming. This is what am trying to do:
1. The user enters some text in the screen and it keeps getting added to a
UITableView.
2. As usual, it's getting added *from* the top.
3. But I want to add it from the bottom i.e. each new message that's added
is added *above
.
On 25/03/2012, at 5:34 AM, Doug Clinton wrote:
I don't know if this was the issue that Steven was asking about, but I've
been wondering if there is a recommended way to persist the undo stack so
that it's still available if you restart the app, or close and re-open the
document
objects in the stack
would cause memory pressure and would be better occupying disc space as they
are only needed at undo/redo time. Good to know that the VM system will take
care of it.
Steven.
On 24 Mar 2012, at 01:04, Graham Cox wrote:
You can read and write to the Application Support
On 25/03/2012, at 5:34 AM, Doug Clinton wrote:
I don't know if this was the issue that Steven was asking about, but I've
been wondering if there is a recommended way to persist the undo stack so
that it's still available if you restart the app, or close and re-open the
document. It's
fairly easy to exhaust your address space if all deleted files are kept
in-memory.
On 26 Mar 2012, at 00:57, Steven wrote:
Thanks for the info Graham.
I'm using NSUndoManager. I thought that many large objects in the stack
would cause memory pressure and would be better occupying disc
I don't know if this was the issue that Steven was asking about, but I've been
wondering if there is a recommended way to persist the undo stack so that it's
still available if you restart the app, or close and re-open the document. It's
always bothered me that there is this great mechanism
Thanks for the info Graham.
I'm using NSUndoManager. I thought that many large objects in the stack would
cause memory pressure and would be better occupying disc space as they are only
needed at undo/redo time. Good to know that the VM system will take care of it.
Steven.
On 24 Mar 2012
Hello,
Where is the correct place to store an on-disc undo stack associated with a
NSDocument instance ?
The stack may contain several potentially large files so we don't want them to
occupy memory.
For a compound document the stack could reside in a directory NSFileWrapper.
For a single file
You can read and write to the Application Support folder.
But FILES in an Undo stack? That makes little sense to me.
If you want to undo changes to a file, store the changes or the command that
will cause the changes in the undo stack. If you are changing the organisation
of files on disc
to
uncaught exception 'NSInternalInconsistencyException', reason: 'Cannot create
NSArray from object NSManagedObjectContext: 0x10192d020 of class
NSManagedObjectContext'
*** First throw call stack:
(
0 CoreFoundation 0x7fff8c551286
__exceptionPreprocess + 198
1
Please don't cross-post.
On Jan 1, 2012, at 9:26 AM, Ayers, Joseph wrote:
I have a program crashing loading a NIB that isn't explicitly specified. The
call frame is below From the call frame it looks like it's called in line 8.
How do I reveal the name of the nib file?
Probably you should
[Stripped xcode-users from the recipients. Do not cross-post.]
On 1 Jan 2012, at 9:26 AM, Ayers, Joseph wrote:
5 AppKit 0x7fff86718a0f
-[NSObject(NSKeyValueBindingCreation) bind:toObject:withKeyPath:options:] +
591
6 AppKit
For some reason the APP started looping on the window initialization that was
in Init, so I moved it to applicationDidFinishLaunching. Now it doesn't get to
that with the message in GBD:
warning: UUID mismatch detected between:
If you declare a C function as inline, and this function invokes other
functions, does this function appear to invoke itself in the call stack of a
crash report?
See lines 5-8, in this call stack. 'MyFunction' is declared 'inline' and does
not call itself.
Application Specific Information
On Dec 26, 2011, at 4:31 PM, Jerry Krinock wrote:
If you declare a C function as inline, and this function invokes other
functions, does this function appear to invoke itself in the call stack of a
crash report?
See lines 5-8, in this call stack. 'MyFunction' is declared 'inline
Thank you, Ken. You are correct, as usual.
Upon symbolicating, I found the actual problem.
Now, I've been symbolicating crash reports for years, but I do so when I see a
line in a crash report like this:
8 MyFramework 0x000c5c49 0x7000 + 781385
where you see the symbol name is missing.
A good while back, I asked a question about how to get from a byte offset to a
line number:
http://www.cocoabuilder.com/archive/cocoa/276690-debugging-stack-traces.html
Does this information still hold for the latest tools, i.e. LLVM and debugger?
Is it possible to extract the relevant line
Graham Cox graham@bigpond.com wrote on Mon, 3 Oct 2011
at 23:59:15 +1100 in 04d75b8e-913f-4ea0-b9af-403d73b19...@bigpond.com:
Is it possible to extract the relevant line without actually running
the code in the debugger? I ask because I have a situation where I
have a crash report (with
Hi,
I've occasionally noticed after upgrading to Lion that my exception
handling code no longer provides full stack trace, but only some
trimmed piece.
For example, I performed the following experiment. There is an
-emulateCrash: action method, implemented in MyWindowController,
attached
to intervene in code to then disassociate the view from
its delegate. Also, there is no dealloc method where you dispose of
the UIWebView, because that's done automatically when the view is
popped off the navigation stack.
What I do is start with a UIViewController subclass that creates
On Jun 20, 2011, at 8:21 AM, Jeff Kelley wrote:
If you’re creating the web view in -viewDidLoad, you should probably release
it and nil the pointer to it in -viewDidUnload, not -dealloc.
You need to do both. You aren't guaranteed that your -viewDidUnload method will
ever be called, so if you
for the UIWebView is set up in the XIB file; it's pretty
hokey to have to intervene in code to then disassociate the view from
its delegate. Also, there is no dealloc method where you dispose of
the UIWebView, because that's done automatically when the view is
popped off the navigation stack.
What I do
automatically when the view is
popped off the navigation stack.
What object is asking as the web view's delegate? Typically that object also
has an owning reference to the web view, so you likely already have a -dealloc
method that releases the web view – just also set the delegate of the web view
for the UIWebView is set up in the XIB file; it's pretty
hokey to have to intervene in code to then disassociate the view from
its delegate. Also, there is no dealloc method where you dispose of
the UIWebView, because that's done automatically when the view is
popped off the navigation stack.
Does anyone know
On Jun 16, 2011, at 7:15 PM, G S wrote:
The delegate for the UIWebView is set up in the XIB file; it's pretty
hokey to have to intervene in code to then disassociate the view from
its delegate.
If the delegate object is being dealloced, it needs to clear the delegate
reference to it. I
Am 28.04.2011 um 04:31 schrieb Lee Ann Rucker:
It would be nice if there was some sort of built-in combining stack,
especially for the info-only dialogs, the way starting multiple file copies
in the Finder gives you one window with multiple sections instead of multiple
windows.
Why
Oh, it's probably not. So many other interesting things are higher up the
stack, though.
- Original Message -
From: Andreas Mayer andr...@harmless.de
To: cocoa-dev@lists.apple.com
Sent: Thursday, April 28, 2011 5:38:50 AM
Subject: Re: Stack of NSWindow sheets
Am 28.04.2011 um 04:31
Oleg Andreev wrote:
Is there a well-known way (or a library) to keep a stack (or queue) of sheets
per window?
I'm a developer of Gitbox - a git repository manager. It keeps several repos
opened and periodically updates them. If some repos require authentication, a
modal dialog pops up
I've seen an app that uses a stack of sheets in this fashion, and it's a
horrid, barely usable mess. It's a Microsoft app, though I forget exactly which
(and it may have been fixed, as this was quite some time ago).
The problem is that the user either has to remember the path that led them
correctly, I need to maintain some sort
of a queue for these sheets.
On 27 Apr 2011, at 14:58, Graham Cox wrote:
I've seen an app that uses a stack of sheets in this fashion, and it's a
horrid, barely usable mess. It's a Microsoft app, though I forget exactly
which (and it may have been
I swear I've seen this in some open source code – maybe Adium?
On 26 Apr 2011, at 19:55, Oleg Andreev wrote:
Hello,
Is there a well-known way (or a library) to keep a stack (or queue) of sheets
per window?
I'm a developer of Gitbox - a git repository manager. It keeps several repos
On Wed, Apr 27, 2011 at 6:35 AM, Oleg Andreev olega...@gmail.com wrote:
Again, normally you'll see no dialogs at all (when the password is already
stored in keychain) or a single dialog when a new repository is added or the
password was changed. But I should have a nice fallback for a case
On Apr 27, 2011, at 09:35, Oleg Andreev wrote:
I'll clarify what I meant.
Normally, user will see only one sheet at a time. There won't be any sort of
step-by-step sheet switching within a single task (like in Xcode 4 when
creating a new file). The only issue I'm trying to solve is
On Wed, Apr 27, 2011 at 10:16 AM, Gregory Weston gwes...@mac.com wrote:
I increasingly believe you're using the wrong UI for the need you describe.
I'm not confident I have a good guess at what the *right* one is,
unfortunately, but sheets spontaneously opening like this really feels wrong.
are rare enough not to
be too much of a problem.
It would be nice if there was some sort of built-in combining stack, especially
for the info-only dialogs, the way starting multiple file copies in the Finder
gives you one window with multiple sections instead of multiple windows.
- Original
Hello,
Is there a well-known way (or a library) to keep a stack (or queue) of sheets
per window?
I'm a developer of Gitbox - a git repository manager. It keeps several repos
opened and periodically updates them. If some repos require authentication, a
modal dialog pops up. I'd like to clean
On Apr 26, 2011, at 11:55, Oleg Andreev wrote:
2. Is it a good way to solve the problem? Maybe I miss some subtle issues
with AppKit or user experience.
I'd say the difficulty with this approach is that, at any given moment, there
may be a stack of dialogs (of fairly critical importance
Change+UITextfield+on+a+detailview+by+clicking+on+different+Cells
http://stackoverflow.com/q/5134693/623784
Every help appreciated. I'm kinda noob, so forgice me if the answer is
simple;)___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please
My original reply was too long for Cocoa Dev; then I lost it.
So this is another (small draft)...
It appears I'll be working with blocks, keeping the data/functioning local
to the stack copying data out to the GUI:
typedef sat_t (^MyBlock)();
// C - function:
int addFoot(int k
;
...
...
} sat_t;
--
sat_t workingSat;
...
initSatWorkArea(workingSat); --- a NSObject's method (in head) is accessing
a C-function (on stack)?
However, I'm concerned about memory usage stability.
Am I correct that these C functions are within the Stack vs Heap...
...and thus
Hi,
I have this layout: A container view C, with two sub-views in vertical
order: a Box B on the top, and a WebView W at the bottom.
Box B
---
WebView W
In IB, I set the following resize property:
B: fixed top edge and fix height, take whole width of the parent
W: fixed
On Thu, Oct 21, 2010 at 10:10 PM, Wayne Shao wsha...@gmail.com wrote:
Hi,
I have this layout: A container view C, with two sub-views in vertical
order: a Box B on the top, and a WebView W at the bottom.
Box B
---
WebView W
In IB, I set the following resize property:
On Jun 29, 2010, at 22:47 , Sean McBride wrote:
I don't believe that's the right pattern. In awakeFromInsert/Fetch, one
should be using primitive setters. The docs say If you want to set
attribute values in an implementation of this method, you should
typically use primitive accessor
On Jun 28, 2010, at 12:33 , Mike Abdullah wrote:
On 27 Jun 2010, at 00:01, Guillaume Laurent wrote:
Hi all,
I'm having difficulties with the undo/redo mechanism and my Core Data
objects. The problem is that I create a CoreData object (say a rectangle),
then set some of its
this in the app, each of the steps of the object's creation are undone
seperately, including the setting of each of the attributes.
Bottom line : is there a way to make it so that the CoreData object's
instantiation and its setup are registered as a single action in the
undo/redo stack ?
I
On 2010 Jun 29, at 13:47, Sean McBride wrote:
I don't believe that's the right pattern. In awakeFromInsert/Fetch, one
should be using primitive setters. The docs say ...
You're correct, Sean. I thought I got that pattern from some Apple sample
code, but I can't find it now.
Use of
On Sat, 26 Jun 2010 19:08:29 -0700, Jerry Krinock said:
Bottom line : is there a way to make it so that the CoreData object's
instantiation and its setup are registered as a single action in the
undo/redo stack ?
I presume that you are setting these attributes in -awakeFromInsert.
One solution
that the CoreData object's
instantiation and its setup are registered as a single action in the
undo/redo stack ? So that instead of having
- new rect with rect.x = 0
- rect.x change from 0 to 100
I can have
- new rect with rect.x = 100
?
Thanks for any replies,
--
Guillaume
http
that the CoreData object's
instantiation and its setup are registered as a single action in the undo/redo
stack ? So that instead of having
- new rect with rect.x = 0
- rect.x change from 0 to 100
I can have
- new rect with rect.x = 100
?
Thanks for any replies,
--
Guillaume
http
seperately,
including the setting of each of the attributes.
Bottom line : is there a way to make it so that the CoreData object's
instantiation and its setup are registered as a single action in the
undo/redo stack ?
I presume that you are setting these attributes in -awakeFromInsert
Hi,
After publishing an update of my app, I have received quite a few
crash dumps with very weird stack traces that I cannot understand and
fix.
Namely, the exception message says that AXTitle, or AXWindow or
AXValue or AXDocument etc. is unsupported by NSWindow, NSOpenPanel,
NSApplication
reports? If so, reply with those to the list and we may be able to
help you.
-corbin
On Feb 2, 2010, at 10:04 AM, Oleg Krupnov wrote:
Hi,
After publishing an update of my app, I have received quite a few
crash dumps with very weird stack traces that I cannot understand and
fix.
Namely
Hi Corbin,
Thanks for your quick response. You are right, I should have been more
specific. This is not a crash in precise meaning. This is an
unhandled exception raised by appkit's accessibility and caught by my
crash reporter facility that prints the stack trace and sends it to me
by e-mail
...@gmail.com wrote:
Hi Corbin,
Thanks for your quick response. You are right, I should have been more
specific. This is not a crash in precise meaning. This is an
unhandled exception raised by appkit's accessibility and caught by my
crash reporter facility that prints the stack trace and sends
crash reporter facility that prints the stack trace and sends it to me
by e-mail. There is no real, severe crash like that one when you see
the Apple's crash report dialog.
The question is -- why this exception is raised? I don't even mention
anything related to AX anywhere in my app. I must
1 - 100 of 209 matches
Mail list logo