search

bahlolab / superSTR

A lightweight, alignment-free utility for detecting repeat-containing reads in short-read WGS, WES and RNA-seq data.
GNU General Public License v2.0
17 stars 7 forks source link

stack smashing detected #21

Closed wdecoster closed 10 months ago

wdecoster commented 10 months ago

Hi,

I realize that this gives you very little information to debug, so please let me know what I can do to gather more information about this error. I installed superSTR using conda (mamba), and I am running this using slurm on BAM files. My jobs end up with a non-zero exit code after a few hours, printing to stderr:

*** stack smashing detected ***: <unknown> terminated
srun: error: mforge157: task 0: Aborted (core dumped)

Do you have an idea of how to solve this?

Wouter

lfearnley commented 10 months ago

Just double checking - strdust or superSTR?

On Tue, 7 Nov 2023, 6:06 am Wouter De Coster, @.***> wrote:

Hi,

I realize that this gives you very little information to debug, so please let me know what I can do to gather more information about this error. I installed strdust using conda (mamba), and I am running this using slurm on BAM files. My jobs end up with a non-zero exit code after a few hours, printing to stderr:

stack smashing detected : terminated srun: error: mforge157: task 0: Aborted (core dumped)

Do you have an idea of how to solve this?

Wouter

— Reply to this email directly, view it on GitHub https://github.com/bahlolab/superSTR/issues/21, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC25LCKZEPDDIOD2ZJWNZQLYDII27AVCNFSM6AAAAAA7A7XDMWVHI2DSMVQWIX3LMV43ASLTON2WKOZRHE4DCMBZHE3DIOA . You are receiving this because you are subscribed to this thread.Message ID: @.***>

wdecoster commented 10 months ago

Oh. Let me fix that :-D

lfearnley commented 10 months ago

Haha, I know that feeling!

We haven't encountered a stack smash yet and will need to a bit of additional information.

I think the first step for debug will be to build from source with the -g flag, see if it still faults, and if so, try it under valgrind if available using exp-sgcheck.

This should give a stack trace that'll be informative as to where things are going awry.

On Tue, 7 Nov 2023, 6:38 am Wouter De Coster, @.***> wrote:

Oh. Let me fix that :-D

— Reply to this email directly, view it on GitHub https://github.com/bahlolab/superSTR/issues/21#issuecomment-1798335910, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC25LCOO53C2HDQPSP4JC7TYDIMUXAVCNFSM6AAAAAA7A7XDMWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJYGMZTKOJRGA . You are receiving this because you commented.Message ID: @.***>

wdecoster commented 10 months ago

I think the first step for debug will be to build from source with the -g flag, see if it still faults

That already solved the problem :)