Opened 11 years ago

Closed 11 years ago

#3608 closed Bug (invalid)

transmission-daemon:" Cannot initialize thread debugging library: generic error"

Reported by: hooky-mars Owned by:
Priority: Normal Milestone: None Set
Component: Daemon Version: 2.04
Severity: Critical Keywords:
Cc:

Description

I have trouble with Transmission-daemon 2.04:

#gdb transmission-daemon
GNU gdb 6.8
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "mipsel-linux-uclibc"...
(gdb) start -f
Breakpoint 1 at 0x409880: file ../../daemon/daemon.c, line 314.
Starting program: /tmp/hdd/volumes/HDD2/bin/transmission-daemon -f
warning: Cannot initialize thread debugging library: generic error
warning: Cannot initialize thread debugging library: generic error
warning: Cannot initialize thread debugging library: generic error
main (argc=0, argv=0x0) at ../../daemon/daemon.c:314
314     ../../daemon/daemon.c: No such file or directory.
        in ../../daemon/daemon.c
(gdb) quit
The program is running.  Exit anyway? (y or n) y

What does I must do to get rid of it?

Change History (4)

comment:1 Changed 11 years ago by charles

If you're referring to "Cannot initialize thread debugging library: generic error," -- this doesn't appear to be a transmission issue. Googling for that phrase yields a lot of hits for people running a uclibc-built gdb on all kinds of programs unrelated to Transmission.

comment:2 Changed 11 years ago by charles

  • Component changed from Transmission to Daemon
  • Summary changed from Transmission-daemon doesn`t work to transmission-daemon:" Cannot initialize thread debugging library: generic error"

comment:4 Changed 11 years ago by charles

  • Resolution set to invalid
  • Status changed from new to closed

This appears to be a config issue answered by KyleK in the forums, rather than a bug/feature to be handled in trac. Closing this ticket... but I'm glad you got an answer in the forums :)

Note: See TracTickets for help on using tickets.