pathologic error: linux-vdso.so.1: No such file or directory

edit

Hi, Thank you for waiting. I don't have an answer for this, but could you provide the details from the pathologic log file with the error - what was pathologic doing, where there any stack trace or other details from the error.

Here's the tail end of the log file, there's no way for me to post or attach the whole thing. The line prior to what's pasted here exceeds the allowed characters. There are no further error messages given, in the terminal the command would appear to complete successfully. 109555040 bytes have been tenured, next gc will be global. See the documentation for variable EXCL:*GLOBAL-GC-BEHAVIOR* for more information. 20 40 linux-vdso.so.1: No such file or directory

Note that previous comment is standard output/error. I forgot that pathologic creates a separate log file. The output there is quite verbose, evaluation stack points to: ->(TPL::ZOOM-COMMAND :FROM-READ-EVAL-PRINT-LOOP NIL ...) There are then many lines like this: (READ-BROKEN-SEQUENCE 1305806 4 ...) (READ-GENE-SEQUENCE 1305806 4 ...) Which to me suggests a problem with the input files, but I can't find any issue with how they're formatted (worked fine with previous versions of pathway-tools).

Hi, Could you please send that other file to ptools support. Also, we are looking into this. Apparently linux-vdso.so.1 is not a regular library, but a virtual library generated by the linux kernel (https://unix.stackexchange.com/questions/396987/is-the-vdso-shared-library-linux-vdso-so-the-library-that-contains-the-kernel). Could you also try running blast and see if that's operating correctly.

Many thanks, I actually preemptively sent both log files to ptools support after my initial post. Let me know if not easily found and I'll resend. I've confirmed that eutils works (via a call from within Biopython) and blast is functional.