Re: GDB crashing
Re: GDB crashing
- Subject: Re: GDB crashing
- From: Philip Aker <email@hidden>
- Date: Mon, 16 Apr 2007 00:31:37 -0700
On 2007-04-15, at 07:09:08, Ed Martin wrote:
I guess i need to explain a bit more, i really just wanted to know
if it is considered "normal" and acceptable for gdb to exit on an
assert() (in gdb itself) when debugging a program, i was under the
impression that no matter how bad your application is gdb should
not crash and should instead stop the program or print a message
when gdb can no longer control it (because of something like a
messed up stack), or at least something close
Not too sure. I try to mind my P's and Q's and catch as much as
possible at compile time by upping the compiler restrictions and
occasionally inserting the odd printf() or CFShow() to view non-
obvious things. Jim Ingham has substantial knowledge of gdb, and
occasionally posts to this list. I think Scott's observation about
the origin of your crash is a good one though…
@Philip Aker
In my application i needed an arbitrary number of rows and columns
(my largest test case is actually a 1000x1000 table), so i can't do
a switch, instead i decided to set kColFirst = 'A\0\0\0' and add/
subtract that to the property ID, so i can pass it through the
Apple stuff as a valid ID (it would give me the largest span of
"valid" IDs), and later pass it through my stuff by using that as
an offset
I see. I actually do the same myself in other circumstances but have
not had the need in DataBrowser.
Since you haven't supplied any code for anyone to verify, have you
set up a scenario which proves the DataBrowser implementation works
sans matrix allocation?
Philip Aker
email@hidden
_______________________________________________
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