[Debian-med-packaging] Bug#905206: Seems to crash in fortran lib
olivier sallou
osallou at debian.org
Thu Oct 3 11:35:07 BST 2019
Le jeu. 3 oct. 2019 à 12:08, Michael Crusoe <michael.crusoe at gmail.com> a
écrit :
> On Sat, 9 Mar 2019 17:44:02 +0100 olivier sallou <osallou at debian.org>
> wrote:
> > Looking at core generated file and using gdb we see that it fails in
> > fortran lib.
> >
> > Either program tries something wrong in a fortran updated lib version,
> > either the fortran lib is itself buggy.
> >
> > I have no fortran knowledge to debug this however. And it lacks debug
> info
> > to find calling line in profnet.
>
> The debug symbols exists for non-amd64 archs:
> https://packages.debian.org/sid/profnet-snapfun-dbgsym
>
Fun to see it in different arch but not amd64... Will give a try when
possible.
> So you can make your own debug symbols locally by rebuilding the package,
> or someone could upload a new source package as it has been almost a year.
> I made some cosmetic cleanups to the Debian packaging if that is a good
> enough excuse (though snapfun still segfaults for me)
>
> >
> > Test: rofnet_snapfun switch 385 55 10 46 100 PROFin.dat PROFacc_tst.jct
> > none dbg
> >
> > Gdb result:
> >
> > Core was generated by `profnet_snapfun switch 385 55 10 46 100 PROFin.dat
> > PROFacc_tst.jct none dbg'.
>
> --
> Michael
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/debian-med-packaging/attachments/20191003/69d55e0d/attachment-0001.html>
More information about the Debian-med-packaging
mailing list