corrupted double-linked list

Get help, report and discuss bugs.
Post Reply
nobody

corrupted double-linked list

Post by nobody » 27 Jun 2008, 04:13

I ran into this error just before nzbget crashed today:

$ nzbget --server
[INFO] nzbget server-mode
[INFO] Collection x.nzb found
*** glibc detected *** corrupted double-linked list: 0x00139738 ***
Killed

I tried to get a gdb backtrace, but as usual, it didn't look very helpful:
(gdb) bt
#0 0x404236e4 in kill () from /lib/libc.so.6
#1 0x4019c214 in pthread_kill () from /lib/libpthread.so.0
#2 0x4019c24c in raise () from /lib/libpthread.so.0
#3 0x40423524 in raise () from /lib/libc.so.6
#4 0x404244f0 in abort () from /lib/libc.so.6
#5 0x404244f0 in abort () from /lib/libc.so.6
[...many more repeats of the last line...]


hugbug

RE: corrupted double-linked list

Post by hugbug » 27 Jun 2008, 07:04

>$ nzbget --server
>[INFO] nzbget server-mode
>[INFO] Collection x.nzb found
>*** glibc detected *** corrupted double-linked list: 0x00139738 ***
>Killed

1. Was it the first nzb-file after the start of nzbget or you removed some log-lines?

2. Please check the log-file. The screen-output is updated with a delay; log-file may contain additional entries. Were any files of collection x.nzb downloaded vefore crash?

3. If the line "[INFO] Collection x.nzb found" was the last in the log, it could mean an error on file parsing. Can that nzb-file be loaded on next program or it always fails? If it fails always, please send me the file.

forest

RE: corrupted double-linked list

Post by forest » 24 Jul 2008, 03:57

1. It was the first nzb-file after startup. The output I copies above was not from the log file, but to the console.

2. The log file was short, without any obvious explanation of the crash. I don't remember what was in it.

3. I no longer have the nzb file.

I rebuilt nzbget-0.4.1-testing with --enable-debug, and was able to complete the download.

hugbug

RE: corrupted double-linked list

Post by hugbug » 24 Jul 2008, 06:18

Thanks for the info.
I can't do anything at the moment.
Please report if you get the error again.

Post Reply

Who is online

Users browsing this forum: No registered users and 56 guests