Hello again,
another package originated at RostLab is currently creating issues
as it is reported against the package profphd
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942064#17).
The bug report quotes the following hint:
Make prof work with Debian Jessie by requiring perlbrew packag
Hello,
back in 2009 Laszlo Kajan did quite some effort to package several
projects from rostlab.org for official Debian. There was a very good
cooperation between RostLab and Debian - mediated by Laszlo who was
introducing other members (who probably left Rostlab meanwhile to find
other jobs).
S
On 10/4/19 3:07 PM, Andreas Tille wrote:
> Hi Olivier,
>
> On Fri, Oct 04, 2019 at 02:14:02PM +0200, olivier sallou wrote:
>>> Program received signal SIGSEGV: Segmentation fault - invalid memory
>>> reference.
>> I really do not see what error could be. Maybe a fortran issue after an
>> upgrade
Hi Olivier,
On Fri, Oct 04, 2019 at 02:14:02PM +0200, olivier sallou wrote:
> > Program received signal SIGSEGV: Segmentation fault - invalid memory
> > reference.
>
> I really do not see what error could be. Maybe a fortran issue after an
> upgrade (something that was working but not done the sa
Le jeu. 3 oct. 2019 à 12:58, Michael Crusoe a
écrit :
> Here is the crash with debug symbols (courtesy libc6-dbg libgfortran5-dbg
> and a locally created profnet-snapfun-dbgym)
>
> root@mrc-tux:/tmp# profnet_snapfun switch 385 55 10 46 100 PROFin.dat
> PROFacc_tst.jct none
>
> Program received si
Here is the crash with debug symbols (courtesy libc6-dbg libgfortran5-dbg
and a locally created profnet-snapfun-dbgym)
root@mrc-tux:/tmp# profnet_snapfun switch 385 55 10 46 100 PROFin.dat
PROFacc_tst.jct none
Program received signal SIGSEGV: Segmentation fault - invalid memory
reference.
Backtr
Le jeu. 3 oct. 2019 à 12:08, Michael Crusoe a
écrit :
> On Sat, 9 Mar 2019 17:44:02 +0100 olivier sallou
> 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 th
On Sat, 9 Mar 2019 17:44:02 +0100 olivier sallou 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 debu
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 profn
9 matches
Mail list logo
