Unconfigured Ad

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • labrat73
    Member
    • Nov 2010
    • 12

    #1

    Segmentation fault, cuffdiff

    Greetings,

    I am trying to run cuffdiff and at each attempt am met with the message "Segmentation fault".

    I have seen at least two posts from users who encountered the same message, but have not seen any replies addressing this problem.

    I would greatly appreciate any assistance.

    Many thanks!
  • nimmi
    Member
    • Jul 2010
    • 15

    #2
    I am also encountering the same problem. It would be great if someone can suggest a solution to this.

    Thanks in advance.

    Comment

    • adarob
      Member
      • Jul 2010
      • 71

      #3
      At what point in the process does the fault occur? What is the output that surrounds it?

      Please PM me if you have a (preferably small) dataset that exhibits this issue and you're willing to upload it for me to recreate the error.

      Comment

      • nimmi
        Member
        • Jul 2010
        • 15

        #4
        Hi,
        Thank you for your response.

        Here is the command that I am using:

        cuffdiff -o ucsc_refseq.gtf sample1_accepted_hits.sam sample2_accepted_hits.sam

        Each *.sam file is ~50G so not sure if I can upload them.

        Best Regards
        Nirmala

        Comment

        • adarob
          Member
          • Jul 2010
          • 71

          #5
          Where in the process is it when it crashes?

          Comment

          • nimmi
            Member
            • Jul 2010
            • 15

            #6
            It stops immediately giving a segmentation fault error

            Comment

            • pbseq
              Member
              • Feb 2010
              • 16

              #7
              in cuffdiff, the -o option should be followed by the results output directory, not by the transcript gtf file. try deleting -o in your command:
              cuffdiff -o ucsc_refseq.gtf sample1_accepted_hits.sam sample2_accepted_hits.sam

              Comment

              • nimmi
                Member
                • Jul 2010
                • 15

                #8
                Sorry it was a typo in my previous post. Here's the command:

                cuffdiff -o cuffDiffOutput ucsc_refseq.gtf sample1_accepted_hits.sam sample2_accepted_hits.sam

                Comment

                • gzhao
                  Junior Member
                  • Apr 2011
                  • 1

                  #9
                  I just find out that the output directory must not already exist when you run the cuffdiff command. If it's already there cuffdiff will give segmentation fault. cuffdiff will create it.
                  Last edited by gzhao; 04-18-2011, 09:02 AM.

                  Comment

                  • lshen
                    Member
                    • Jan 2008
                    • 30

                    #10
                    Originally posted by gzhao View Post
                    I just find out that the output directory must not already exist when you run the cuffdiff command. If it's already there cuffdiff will give segmentation fault. cuffdiff will create it.

                    You are right. I got same issue in version v1.0.1 after I run cuffmerge, but at first I thought it is some issue with the merged tanscripts.gtf.

                    Comment

                    • lshen
                      Member
                      • Jan 2008
                      • 30

                      #11
                      If the folder name for -o i cuffdiff is long, I also got same error message. I used a shorter name worked fine.

                      Comment

                      • kaus
                        Junior Member
                        • Dec 2014
                        • 2

                        #12
                        same problem - can't fix

                        I'm using cuffdiff for the first time and got the segmentation fault error. Someone suggested it might be a memory issue but I'm using a MacPro 16G RAM and 8 cores so I don't think that's it. As for the output file thing as suggested by gzhao and Ishen, I removed that option altogether (as well as all other options) so output should be in the default directory. Still doesn't work. I've tried using both Cufflinks 2.2.0 and 2.2.1.
                        Any help will be greatly appreciated.

                        Comment

                        • dog941013
                          Junior Member
                          • Mar 2018
                          • 1

                          #13
                          I got the same problem but it turns out I didn't include the label option. Maybe you can try with the -L commend

                          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, Yesterday, 11:13 AM
                          0 responses
                          16 views
                          0 reactions
                          Last Post SEQadmin2  
                          Started by SEQadmin2, Yesterday, 10:48 AM
                          0 responses
                          16 views
                          0 reactions
                          Last Post SEQadmin2  
                          Started by SEQadmin2, 10-15-2026, 10:52 AM
                          0 responses
                          35 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...