Line number of an error

[Jean-Luc Arnaud]

Hi all,

Using Exception and, maybe, an Introspection function, is there a way to
get the line number of an error?

MBS functions welcome, too.

TIA

[Valerio Pittavino]

You should use the stack calls

Inviato da iPhone

Post by Jean-Luc Arnaud
Hi all,
Using Exception and, maybe, an Introspection function, is there a way to get the line number of an error?
MBS functions welcome, too.
TIA
--
Jean-Luc Arnaud

To unsubscribe, email ***@xojo.com

[Jean-Luc Arnaud]

Thanks for your reply, Valerio.

Could you please give me more detailed information? Maybe a sample code?

TIA

Jean-Luc Arnaud

Post by Valerio Pittavino
You should use the stack calls
Inviato da iPhone

Post by Jean-Luc Arnaud
Hi all,
Using Exception and, maybe, an Introspection function, is there a way to get the line number of an error?
MBS functions welcome, too.
TIA
--
Jean-Luc Arnaud

To unsubscribe, email ***@xojo.com

[Valerio Pittavino]

Hi,
download this
https://www.dropbox.com/s/leac8whom8iv37m/untitled.xojo_binary_project?dl=0
you can't see the line that has the error but is not complicated to
understand the error position using the stack list and the information in
class RunTimeException.
This is useful to send some reports about problem about distribuited
softwares

Post by Jean-Luc Arnaud
Thanks for your reply, Valerio.
Could you please give me more detailed information? Maybe a sample code?
TIA
Jean-Luc Arnaud

Post by Valerio Pittavino
You should use the stack calls
Inviato da iPhone
Il giorno 24 ago 2017, alle ore 16:36, Jean-Luc Arnaud <

Post by Jean-Luc Arnaud
Hi all,
Using Exception and, maybe, an Introspection function, is there a way to
get the line number of an error?
MBS functions welcome, too.
TIA
--
Jean-Luc Arnaud

[Jean-Luc Arnaud]

Thanks a lot, Valerio.

Seems very interesting!

Jean-Luc Arnaud

Post by Valerio Pittavino
Hi,
download this
https://www.dropbox.com/s/leac8whom8iv37m/untitled.xojo_binary_project?dl=0
you can't see the line that has the error but is not complicated to
understand the error position using the stack list and the information
in class RunTimeException.
This is useful to send some reports about problem about distribuited
softwares
Thanks for your reply, Valerio.
Could you please give me more detailed information? Maybe a sample code?
TIA
Jean-Luc Arnaud
You should use the stack calls
Inviato da iPhone
Il giorno 24 ago 2017, alle ore 16:36, Jean-Luc Arnaud
Hi all,
Using Exception and, maybe, an Introspection function, is
there a way to get the line number of an error?
MBS functions welcome, too.
TIA
--
Jean-Luc Arnaud
--
Valerio Pittavino

To unsubscribe, email ***@xojo.com

[Jon Ogden]

This post might be inappropriate. Click to display it.

[Bernd Fröhlich]

I’ve got one case where I get an NOE and I have been completely unable to find out where it happens.

I had such a case once. Turned out to be a race condition.

On my computer it never happened but on a (faster) users computer the order of events appeared to be different and one part of my program that another part of the program relied on having finished in fact had not finished.

Once I found the problem, it was quite easy to fix. The hard part is indeed finding out what is wrong and why it only happens sometimes.

Greetings from Germany,
Bernd Fröhlich


To unsubscribe, email ***@xojo.com

[Jon Ogden]

Post by Bernd Fröhlich

I’ve got one case where I get an NOE and I have been completely unable to find out where it happens.

I had such a case once. Turned out to be a race condition.
On my computer it never happened but on a (faster) users computer the order of events appeared to be different and one part of my program that another part of the program relied on having finished in fact had not finished.
Once I found the problem, it was quite easy to fix. The hard part is indeed finding out what is wrong and why it only happens sometimes.

Could be that but not sure. It’s harmless whatever it is. Seems not to affect operation after the error happens. I just want to know why it happens...



To unsubscribe, email ***@xojo.com

[Jean-Luc Arnaud]

Jon and Bernd,

Yes, it's sometime very hard to find an error.

I had a case where my program worked like a charm on my computer, and
not at all on the user one!!!

My computer runs a French OS, the user one was speaking German...

There are tons of reasons for bugs: logical errors, different OS and
versions of OS, different languages, now 32 and 64bit, textencoding,
numeric imprecision, etc...

A generic code for catching unhandled errors is really mandatory, at
least in pre-release versions.

Jean-Luc Arnaud

Post by Bernd Fröhlich

I’ve got one case where I get an NOE and I have been completely unable to find out where it happens.

I had such a case once. Turned out to be a race condition.
On my computer it never happened but on a (faster) users computer the order of events appeared to be different and one part of my program that another part of the program relied on having finished in fact had not finished.
Once I found the problem, it was quite easy to fix. The hard part is indeed finding out what is wrong and why it only happens sometimes.
Greetings from Germany,
Bernd Fröhlich

To unsubscribe, email ***@xojo.com