Re: FTS Crash

Hi Joseph,

> Then you'd download it, crash it, and send the log file it makes to
me. It would just consist of lots of lines like
> Reached line such and such
> Reached line such and such, relevant variables such and such,
> etc.
>

> Well, this is no problem. Just tell me exactly what to do...

Thanks, really appreciate it.

> I'll try the newest beta first, just to see if it works any better...
> by comparison, now the "older" one is a disappointment!

Yes, I have fixed a few bugs in it, not ones that caused crashes here,
but you never know.

> > This isn't completely guaranteed to work because occasionally in
> this situation,adding in debug code can change it enough to stop it
> from crashing

> This is funny... well, ok, it's funny to ME, but it wouldn't be very
> funny to anyone programming the thing...

Yes, I can see the humerous side of it. Can indeed be frustrating
when you've put a whole lot of debug code in, then have to take it out again
and try another tack. :-)

Can happen esp. when debugging something that depends on relative
timing of parts of the prog. and the debug code slows it down just
enough to stop the bug happening. Or else, because the bug is result
of attempt to access memory that does belong to the prog. but
not the area it should be using, so what is in the memory causes the crash,
and depends on what was done in the previous lines, which changes
because of the debug code and prevents the crash... }:-(

>
> > Making sure FTS doesn't crash is my top priority, so I hope you can
> help with this, - nobody else has yet reported this bug to me.
> >
> Well, I can't imagine there's anything that "special" about my own
> setup...

Could be something like version numbers of the dlls maybe, - a
windows program is "an extension of the operating system" to
quote Charles Petzold.

Or who knows, maybe your mouse driver even;
there's lots of detail involved in the environment a Windows program works in.

(I've got a new mouse which is v. frustrating because it keeps ignoring
mouse moves, and doing double clicks at random instead of single clicks
- an unwise "bargain" fancy optical mouse!)

Change anything, and if the program is a bit delicate because of a bug,
there is then a possibility it could crash.

> I'll try the most recent beta, hopefully this evening (NYC time)...

Thanks again,

I am just doing another upload of the beta right now this minute.

Has option to play drones now, for Scottish bagpipes, or Sitar.

Robert

--- In tuning@egroups.com, "Robert Walker" <robert_walker@r...> wrote:

http://www.egroups.com/message/tuning/15998

Hi Robert...

Well, I just downloaded the new beta Smithy right now. It's 9:40PM
New York time, so it means it's 3:40AM your time... Gee, you work
really late... or EARLY!

Ummm. It crashes again. Same thing...both in playing scales and
playing "seeds."

So, I uninstalled the entire thing and went back to the older
"authenticated" version of Smithy, since I cannot now be without a
working version of Smithy!

It seems like the earlier version of the beta worked for me just
fine... I wonder what's happening?

Well, perhaps a "crash-beta" is in order, with clear instructions as
to post-demolition...

_______ ___ __ __ _
Joseph Pehrson