"how to allow a classical installation of o-charts_pi replacing oernc_pi and oesenc_p

[filochard]

Now I'm gonna try an simple install without building rpms

[bdbcat]

filochard...


If you make o-charts_pi as debug build (cmake -DCMAKE_BUILD_TYPE=Debug ..), then you can run OCPN under gdb or ddd to discover the exact crash location by backtrace.


Dave

[filochard]

Hi Dave

Very strange thing
I have rebuilt my o-charts_plugin rpm (version 1.0.25.0) after having only added -DCMAKE_BUILD_TYPE=Debug in the cmake line of the spec file...

I reinstalled the rpms (built upon wxgtk3.1.5) of OpenCPN s63_pi o-charts_pi sar_pi radar_pi route_pi

I runned Opencpn 5.6.2 inside gdb
I activated o-charts_pi and actualized my charts list
no crash !!!

Then I stopped opencpn, stopped gdb,
I erased /home/myname/.opencpn
I launched again opencpn inside a console
I activated o-charts_pi and actualized my charts list
no crash !!!
and now the /.opencpn/o_charts_pi/ folder contains ChartImage-xxx files

I don't understand why the simple fact to add -DCMAKE_BUILD_TYPE=Debug
in the spec file solved the crash

Sorry for such a noise for that weird aporia !
Now I can use o-charts_pi with a classical install and may propose to update the whole stuff !

Thanks a lot for your help and for the time you wasted for this

We may change the title of this thread with this one :
"Thanks to Dave (bdbcat) no more problem to replace oernc_pi and oesenc_pi with o-charts_pi"

[bdbcat]

filochard....
I am glad we are making some progress.
We can both be pretty sure that the o-charts_pi is compatible with Fedora-based systems now. The fault, whatever it is, probably has nothing to do with the hand-crafted RPM packaging workflow. Agree?


However, building the o-charts plugin in "Debug" mode does have serious effects on its performance. So, we still need to get to the bottom of this problem.


Did you try running OCPN under gdb (plugin built in normal Release mode), and getting a backtrace on the fault?


Dave

[filochard]

Hi Dave

Everything is OK now : I uninstalled my debug packages letting only the normal packages installed

I launched normally OpenCPN and o-charts_pi works perfectly on a fresh install (creating a new /home/myname/.opencpn/folder)

I then tested if I could even use (instead of this new created folder that I have erased for this test) my previous /home/myname/.opencpn that I had backuped
(my previous config and charts are still OK)

I digged a liittle more and I found why I got segfaults with my first trial to create a rpm by cherry picking the components :
I made a very big and stupid mistake
Instead of simply using :
cmake -B .
make

I had used :
cmake -B .
make tarball

The libo-charts_pi.so that I had cherry picked then was not built to be used inside a classical install but with the plugin manager

I'm very sorry to have made such a noise for such a mistake of mine !!!

Nevertheless the good news is that with a correct workaround I can continue building rpms for updating previous rpm installations
And the other good news is the fact that for what I have already tested everything can be built upon wxgtk3.1.5
(I have not yet rebuilt and tested logbookkonni whose I know that in the past it caused segfaults when built upon wxgtku3.1... its code seems needing to be someway modified to be complient with wxgtk3.1.x)


Thanks again for your patience
filochard

[filochard]

By the way
I don't know how to modify the title of this thread
It would be something else such as
"how to allow a classical installation of o-charts_pi replacing oernc_pi and oesenc_pi"

[bcn]

Originally Posted by filochard

By the way
I don't know how to modify the title of this thread
It would be something else such as
"how to allow a classical installation of o-charts_pi replacing oernc_pi and oesenc_pi"

Ask the moderators - click the triangle with the "!" on the left bottom side of the entry...

[JPA Cate]

The OP has requested the title of this thread be changed to "how to allow a classical installation of o-charts_pi replacing oernc_pi and oesenc_pi", and that is how it will appear from this post onwards.

Ann
JPA Cate, moderator