segmentation fault / memory access violation
lazarus / 62-General

----------------------------------------------------------------------
Hans-Josef.Heck · 2015-06-20 19:01

My first visit  and  my first question  on this forum:

I am using my booking program for years now - on linux as well as on
windows.
- written and compiled of course with fpc.

On a new hardware with uefi-bios and a new version of openSUSE Linux
13.1 and 13.2
the program started but then ended with:
"Speicherzugriffsfehler" = "segmentation fault / memory access
violation".

I used my old machine to accomplish the task, as in all the years
before
and moved the output to my new machine.

I kept searching for the problem on the internet all day long, but I
couldn't find a hint.

 -  Is it the UEFI, that - inhibits access  or  something else?
 -  Are -perhaps- libraries missing   ?
 -  What else could cause the problem  ?

Thanks for your help

Hans-Josef  Heck
Wissenschaffen und Handeln

----------------------------------------------------------------------
howardpc · 2015-06-20 19:30

You can either share the code and so get eyes here to debug it for
you, or debug it yourself.
Compile with debugging information, open a Call Stack window (and
perhaps Watches, Local Variables etc. as you need) and single step in
the debugger, starting from your main form's OnCreate or OnShow
handler (or some other event that suits your case), until you reach
the statement(s) that give rise to the access violation. Once you have
pinpointed where the problem lies, you'll probably be able to figure
out what needs amending to cure it. If not, come back here.

----------------------------------------------------------------------
taazz · 2015-06-20 20:09

Quote from: Hans-Josef.Heck on June 20, 2015, 09:01:44 pm -  Is it the
UEFI, that - inhibits access  or  something else?

No, there is no way.

Quote from: Hans-Josef.Heck on June 20, 2015, 09:01:44 pm -  Are
-perhaps- libraries missing   ?

It is probable although you should see a message that the XXXXX.SO
could not be loaded or something along those lines.

Quote from: Hans-Josef.Heck on June 20, 2015, 09:01:44 pm -  What else
could cause the problem  ?
Newer SO that is not compatible with the old one or was compiled with
different parameters, if nothing else changed on your app.