#2170 closed Bug (fixed)
Segfault when accessing torrent Properties
Reported by: | 103450 | Owned by: | charles |
---|---|---|---|
Priority: | Normal | Milestone: | 1.72 |
Component: | GTK+ Client | Version: | 1.70 |
Severity: | Major | Keywords: | |
Cc: |
Description
transmission[11937]: segfault at 0 ip (null) sp 00007fff6f9e4688 error 14 in transmission[400000+c0000] transmission[18832]: segfault at 0 ip (null) sp 00007fffd42f94c8 error 14 in transmission[400000+c0000] transmission[8568]: segfault at 0 ip (null) sp 00007fffdee2a608 error 14 in transmission[400000+c0000]
Built from 1.70 tarball with ./configure --disable-daemon --enable-libnotify --enable-gtk --prefix=/usr
Is it necessary to disable the terminal client if I build the gtk client? Ubuntu 9.04 2.6.30-rc8 kernel
Need any other info let me know.
Change History (8)
comment:1 Changed 14 years ago by charles
- Keywords needinfo added; gtk segfault transmission removed
comment:2 Changed 14 years ago by 103450
This GDB was configured as "x86_64-linux-gnu"... (gdb) handle SIGPIPE nostop noprint Signal Stop Print Pass to program Description SIGPIPE No No Yes Broken pipe (gdb) r Starting program: /usr/bin/transmission [Thread debugging using libthread_db enabled] [New Thread 0x7f26349457a0 (LWP 28369)] [New Thread 0x7f262962e950 (LWP 28372)] ** Message: executing {"arguments":{"ids":[3],"uploadLimit":320},"method":"torrent-set"} [New Thread 0x7f2626def950 (LWP 28379)] [Thread 0x7f2626def950 (LWP 28379) exited] ** Message: executing {"arguments":{"ids":[3],"uploadLimit":400},"method":"torrent-set"} Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7f26349457a0 (LWP 28369)] 0x0000000000000000 in ?? () (gdb)
I can crash it consistently with changing from 320 to 400 or 400 to 320 upload limit. The New Thread 28379 is a hash check on a different torrent.
comment:3 Changed 14 years ago by charles
you forgot the
(gdb) bt
at the end, which is pretty important. could you give it another go?
comment:4 Changed 14 years ago by charles
- Summary changed from Segfault when accessing torrent Properties or for no apparent reason with gtk-client. to Segfault when accessing torrent Properties
comment:5 Changed 14 years ago by 103450
Starting program: /usr/bin/transmission [Thread debugging using libthread_db enabled] [New Thread 0x7f921466a7a0 (LWP 30887)] [New Thread 0x7f9209353950 (LWP 30890)] Message: executing {"arguments":{"ids":[3],"uploadLimit":320},"method":"torrent-set"}
Message: executing {"arguments":{"bandwidthPriority":1,"ids":[3]},"method":"torrent-set"}
Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7f921466a7a0 (LWP 30887)] 0x0000000000000000 in ?? () (gdb) bt #0 0x0000000000000000 in ?? () #1 0x00000000004356e2 in readResponseIdle (vresponse=0x1b3f220)
at tr-core.c:1324
#2 0x00007f920ffea20a in g_main_context_dispatch ()
from /usr/lib/libglib-2.0.so.0
#3 0x00007f920ffed8e0 in ?? () from /usr/lib/libglib-2.0.so.0 #4 0x00007f920ffeddad in g_main_loop_run () from /usr/lib/libglib-2.0.so.0 #5 0x00007f9212bd0bc7 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0 #6 0x000000000042c424 in main (argc=1, argv=0x7fff2616db78) at main.c:464 (gdb) quit This time switched limit and clicked on Priority then locked up.
comment:6 Changed 14 years ago by charles
- Milestone changed from None Set to 1.72
- Status changed from new to assigned
Thanks for the extra info
comment:7 Changed 14 years ago by charles
- Keywords needinfo removed
- Resolution set to fixed
- Status changed from assigned to closed
fixed for 1.72 in r8668.
comment:8 Changed 14 years ago by charles
- Severity changed from Normal to Major
a gdb backtrace: