Unconfigured Ad

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Lakshmi_ISU
    Junior Member
    • Aug 2013
    • 6

    #1

    Segmentation error (core dumped) in velvetg

    Hi All,
    I'm a newbie to the NGS data analysis and still learning through trial and error!
    I'm running velvetg in Cygwin on my computer (64GB RAM). I keep getting segmentation fault (Core dumped) error
    I have the latest version of velvet and I'm trying to assemble a bamboo genome with illumina data (100bp short reads)

    Please can someone help me? Thanks a lot!
  • winsettz
    Member
    • Sep 2012
    • 91

    #2
    segfault is a pretty vague error. You can try recompiling in debug mode (see the velvet manual for this) and see if you can figure anything out. How's your memory consumption? Does it use up all available memory and then crash?

    Comment

    • Lakshmi_ISU
      Junior Member
      • Aug 2013
      • 6

      #3
      Hi winsettz,
      Thank you for your reply.

      I recompiled in debug mode. I didn't get any additional description of the error except "Segmentation fault (core dumped)". This is the command that I used to recompile:
      "make debug BUNDLEDZLIB=1 MAXKMERLENGTH=99 BIGASSEMBLY=1 LONGSEQUENCES=1 OPENMP=1"
      It didn't use all the available memory. Used only about 5GB and then crashed.

      Then I recompiled again as follows:
      "make BUNDLEDZLIB=1 debug"
      and it worked NO segfault error! I'm not sure if I'm doing the right thing here?

      Thanks!

      Comment

      • winsettz
        Member
        • Sep 2012
        • 91

        #4
        Originally posted by Lakshmi_ISU View Post
        Hi winsettz,
        Thank you for your reply.

        I recompiled in debug mode. I didn't get any additional description of the error except "Segmentation fault (core dumped)". This is the command that I used to recompile:
        "make debug BUNDLEDZLIB=1 MAXKMERLENGTH=99 BIGASSEMBLY=1 LONGSEQUENCES=1 OPENMP=1"
        It didn't use all the available memory. Used only about 5GB and then crashed.

        Then I recompiled again as follows:
        "make BUNDLEDZLIB=1 debug"
        and it worked NO segfault error! I'm not sure if I'm doing the right thing here?

        Thanks!
        I would try recompiling without debug, and leave off one flag at a time (bigassembly, longsequences, etc); something is causing your segfault.

        Comment

        • mastal
          Senior Member
          • Mar 2009
          • 666

          #5
          What kmer lengths are you using for your assembly?

          Velvet uses more memory for longer kmers, and also uses more memory
          when it is compiled with the options BIGASSEMBLY and LONGSEQUENCES.

          Comment

          • Lakshmi_ISU
            Junior Member
            • Aug 2013
            • 6

            #6
            Thanks for your quick reply!
            This is what I got when I recompile with bigassembly:

            $ make BIGASSEMBLY=1
            rm obj/*.o obj/dbg/*.o
            rm: cannot remove `obj/dbg/*.o': No such file or directory
            Makefile:50: recipe for target `cleanobj' failed
            make: [cleanobj] Error 1 (ignored)
            mkdir -p obj
            gcc -Wall -O3 -D MAXKMERLENGTH=31 -D CATEGORIES=2 -D BIGASSEMBLY -c src/tightString.c -o obj/tightString.o
            gcc -Wall -O3 -D MAXKMERLENGTH=31 -D CATEGORIES=2 -D BIGASSEMBLY -c src/run.c -o obj/run.o
            gcc -Wall -O3 -D MAXKMERLENGTH=31 -D CATEGORIES=2 -D BIGASSEMBLY -c src/splay.c -o obj/splay.o
            gcc -Wall -O3 -D MAXKMERLENGTH=31 -D CATEGORIES=2 -D BIGASSEMBLY -c src/splayTable.c -o obj/splayTable.o
            src/splayTable.c: In function ‘inputSequenceArrayIntoSplayTableAndArchive’:
            src/splayTable.c:1060:14: warning: variable ‘refElem’ set but not used [-Wunused-but-set-variable]
            RefInfo refElem;
            ^
            gcc -Wall -O3 -D MAXKMERLENGTH=31 -D CATEGORIES=2 -D BIGASSEMBLY -c src/graph.c -o obj/graph.o
            gcc -Wall -O3 -D MAXKMERLENGTH=31 -D CATEGORIES=2 -D BIGASSEMBLY -c src/run2.c -o obj/run2.o
            gcc -Wall -O3 -D MAXKMERLENGTH=31 -D CATEGORIES=2 -D BIGASSEMBLY -c src/fibHeap.c -o obj/fibHeap.o
            gcc -Wall -O3 -D MAXKMERLENGTH=31 -D CATEGORIES=2 -D BIGASSEMBLY -c src/fib.c -o obj/fib.o
            gcc -Wall -O3 -D MAXKMERLENGTH=31 -D CATEGORIES=2 -D BIGASSEMBLY -c src/concatenatedGraph.c -o obj/concatenatedGraph.o
            gcc -Wall -O3 -D MAXKMERLENGTH=31 -D CATEGORIES=2 -D BIGASSEMBLY -c src/passageMarker.c -o obj/passageMarker.o
            gcc -Wall -O3 -D MAXKMERLENGTH=31 -D CATEGORIES=2 -D BIGASSEMBLY -c src/graphStats.c -o obj/graphStats.o
            src/graphStats.c: In function ‘exportLongNodeSequence’:
            src/graphStats.c:953:4: warning: array subscript has type ‘char’ [-Wchar-subscripts]
            velvetFprintf(outfile, "%c", tolower(nucleotide));
            ^
            gcc -Wall -O3 -D MAXKMERLENGTH=31 -D CATEGORIES=2 -D BIGASSEMBLY -c src/correctedGraph.c -o obj/correctedGraph.o
            gcc -Wall -O3 -D MAXKMERLENGTH=31 -D CATEGORIES=2 -D BIGASSEMBLY -c src/dfib.c -o obj/dfib.o
            gcc -Wall -O3 -D MAXKMERLENGTH=31 -D CATEGORIES=2 -D BIGASSEMBLY -c src/dfibHeap.c -o obj/dfibHeap.o
            gcc -Wall -O3 -D MAXKMERLENGTH=31 -D CATEGORIES=2 -D BIGASSEMBLY -c src/recycleBin.c -o obj/recycleBin.o
            gcc -Wall -O3 -D MAXKMERLENGTH=31 -D CATEGORIES=2 -D BIGASSEMBLY -c src/readSet.c -o obj/readSet.o
            src/readSet.c:38:18: fatal error: zlib.h: No such file or directory
            #include <zlib.h>
            ^
            compilation terminated.
            Makefile:109: recipe for target `obj/readSet.o' failed
            make: *** [obj/readSet.o] Error 1

            Comment

            • Lakshmi_ISU
              Junior Member
              • Aug 2013
              • 6

              #7
              Hi mastal,
              I was using kmer length=31

              Comment

              • mastal
                Senior Member
                • Mar 2009
                • 666

                #8
                Well, it looks like it is crashing with the error
                'src/readSet.c:38:18: fatal error: zlib.h: No such file or directory',

                which explains why it doesn't crash if you compile it with the option
                'BUNDLEDZLIB=1'.

                Comment

                • Lakshmi_ISU
                  Junior Member
                  • Aug 2013
                  • 6

                  #9
                  This time, I recompiled using the cmd:make 'BUNDLEDZLIB=1'
                  So I assume it uses the default maxkmerlength?
                  Anyway, I didn't get a segfault!

                  Thanks a lot for helping me with this!!

                  Comment

                  • mastal
                    Senior Member
                    • Mar 2009
                    • 666

                    #10
                    yes, the default MAXKMERLENGTH is 31.

                    if you want to try a longer kmer length you will have to recompile.

                    Comment

                    • Lakshmi_ISU
                      Junior Member
                      • Aug 2013
                      • 6

                      #11
                      Many thanks! This solved my problem

                      Comment

                      Latest Articles

                      Collapse

                      • SEQadmin2
                        Multiomic Liquid Biopsy: What DNA/RNA Panels Reveal That DNA Alone Can’t
                        by SEQadmin2



                        Tumors contain complex mixtures of cell populations that evolve in response to treatment and host-specific factors. Tissue biopsies provide only static snapshots of a tumor’s state. But what if we could follow that evolution over time using a minimally invasive technique?

                        Liquid biopsies can detect tumor-derived material circulating in the bloodstream, providing a way to study treatment response, detect emerging resistance, and discover new biomarkers. Circulating
                        ...
                        10-14-2026, 09:55 AM
                      • SEQadmin2
                        New Genomics Technologies Take Aim at Long-Standing Limits
                        by SEQadmin2


                        Researchers using sequencing and genomics tools often have to make trade-offs. They can choose between speed or scale, short reads or long-range information, or targeted panels or a view of the whole transcriptome. New technologies that have been released this year are built to address those tough choices.

                        We asked six companies the same four questions to learn about their latest products. The new technologies bring a lot to the table, including rethinking sequencing
                        ...
                        09-28-2026, 10:25 AM

                      ad_right_rmr

                      Collapse

                      News

                      Collapse

                      Topics Statistics Last Post
                      Started by SEQadmin2, 10-22-2026, 11:13 AM
                      0 responses
                      22 views
                      0 reactions
                      Last Post SEQadmin2  
                      Started by SEQadmin2, 10-22-2026, 10:48 AM
                      0 responses
                      19 views
                      0 reactions
                      Last Post SEQadmin2  
                      Started by SEQadmin2, 10-15-2026, 10:52 AM
                      0 responses
                      36 views
                      0 reactions
                      Last Post SEQadmin2  
                      Started by SEQadmin2, 10-14-2026, 05:39 AM
                      0 responses
                      42 views
                      0 reactions
                      Last Post SEQadmin2  
                      Working...