Filter an array by content
J. Landman Gay
jacque at hyperactivesw.com
Fri Jun 21 17:33:51 EDT 2019
On 6/21/19 2:48 PM, Alex Tweedly via use-livecode wrote:
> On 21/06/2019 19:38, J. Landman Gay via use-livecode wrote:
>> My only excuse is that I've been avoiding stepping through the
>> debugger because LC has been crashing when I do that. I've sent in
>> many crash logs but it's only recently I've discovered it happens only
>> with Step Over. It's hard to believe no one else has seen this, which
>> I've been seeing since LC 9 first came out, but that's why I didn't
>> know what was in the variable.
> I've been seeing this too. But it's time to confess my abysmal ignorance
> - how do I get a crash log ?
On Mac, a huge dialog appears with the crash log in it. I select all,
copy, paste into a text document and save it. On Windows I don't know,
but if there's a system log (like Console displays on Mac) it's probably
> (And is it worthwhile me getting some of them to add to the bug reports?)
Good question. I've uploaded maybe 20-25 of them so far. I don't always
bother any more.
>> Now that I've discovered breakpoints don't crash as long as I don't
>> step through, I was able to see what's going on.
I was wrong. Not more than a few minutes ago I crashed after stopping at
multiple breakpoints. It doesn't seem to matter if they're red-dot or
typed. However, it seems to take more repetitions before the crash if
you don't do any stepping.
> Hmmm - I find I have no choice but to step through; the editor/debugger
> so often "freezes" (i.e. when I scroll the text, the line numbers don't
> scroll at the same time).
I see that all the time. If you step over, the dot location fixes itself
at least here. Until the crash, anyway. It doesn't crash right away, it
seems to be a cumulative thing, so you get a few chances before
everything goes down.
This has really been crippling my productivity. I'm sure it's a very
elusive thing to track down but I hope they can find it. If no one else
has a problem, it may be something script-related that both you and I
> So I can't just set another breakpoint further
> down - I have to step over for a while until the place at which I want
> to set the breakpoint scrolls itself into view.
>> If you have experienced crashes during debugging, take a look at
>> https://quality.livecode.com/show_bug.cgi?id=22130 and
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
Jacqueline Landman Gay | jacque at hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
More information about the Use-livecode