Bug 556186 - [abrt] crash in iotop-0.3-2.fc12
Summary: [abrt] crash in iotop-0.3-2.fc12
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: iotop
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Adel Gadllah
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:6e391949
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-17 01:39 UTC by Martin Nyhus
Modified: 2010-01-19 19:37 UTC (History)
1 user (show)

Fixed In Version: 0.4-1.fc11
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-01-19 19:33:26 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (1.47 KB, text/plain)
2010-01-17 01:39 UTC, Martin Nyhus
no flags Details

Description Martin Nyhus 2010-01-17 01:39:33 UTC
abrt 1.0.3 detected a crash.

How to reproduce
-----
1. Launch iotop -P
2. Sort on PRIO column (which should contain processes with PRIO ?)

Comment: Change to sort on column PRIO when it contains processes with PRIO "?". Does not crash when -P is turned off.

backtrace
-----
Summary: TB6e391949 ioprio.py:75:sort_key:IndexError: string index out of range

Traceback (most recent call last):
  File "/usr/bin/iotop", line 16, in <module>
    main()
  File "/usr/lib/python2.6/site-packages/iotop/ui.py", line 361, in main
    main_loop()
  File "/usr/lib/python2.6/site-packages/iotop/ui.py", line 351, in <lambda>
    main_loop = lambda: run_iotop(options)
  File "/usr/lib/python2.6/site-packages/iotop/ui.py", line 267, in run_iotop
    return curses.wrapper(run_iotop_window, options)
  File "/usr/lib64/python2.6/curses/wrapper.py", line 44, in wrapper
    return func(stdscr, *args, **kwds)
  File "/usr/lib/python2.6/site-packages/iotop/ui.py", line 261, in run_iotop_window
    ui.run()
  File "/usr/lib/python2.6/site-packages/iotop/ui.py", line 112, in run
    self.process_list.duration)
  File "/usr/lib/python2.6/site-packages/iotop/ui.py", line 220, in refresh_display
    lines = self.get_data()
  File "/usr/lib/python2.6/site-packages/iotop/ui.py", line 205, in get_data
    processes.sort(key=key, reverse=self.sorting_reverse)
  File "/usr/lib/python2.6/site-packages/iotop/ui.py", line 68, in <lambda>
    (lambda p: p.ioprio_sort_key(), False),
  File "/usr/lib/python2.6/site-packages/iotop/data.py", line 275, in ioprio_sort_key
    return ioprio.sort_key(self.get_ioprio())
  File "/usr/lib/python2.6/site-packages/iotop/ioprio.py", line 75, in sort_key
    return -ord(key[1])
IndexError: string index out of range

Local variables in innermost frame:
key: ?

cmdline: /usr/bin/python /usr/bin/iotop -o
component: iotop
executable: /usr/bin/iotop
kernel: 2.6.31.9-174.fc12.x86_64
package: iotop-0.3-2.fc12
uuid: 6e391949

Comment 1 Martin Nyhus 2010-01-17 01:39:35 UTC
Created attachment 384872 [details]
File: backtrace

Comment 2 Adel Gadllah 2010-01-17 10:41:51 UTC
(In reply to comment #0)
> abrt 1.0.3 detected a crash.
> 
> How to reproduce
> -----
> 1. Launch iotop -P
> 2. Sort on PRIO column (which should contain processes with PRIO ?)
> 
> Comment: Change to sort on column PRIO when it contains processes with PRIO
> "?". Does not crash when -P is turned off.

It should contain the io prio (that can be set/read using ionice) not the same prio used by the cpu scheduler (the one that can be set using nice).

I cannot reproduce this.

Could you please try with 0.4 from updates-tesing?

yum --enablerepo=updates-testing update iotop

Thanks

Comment 3 Martin Nyhus 2010-01-17 13:42:03 UTC
0.4 from updates-testing doesn't crash. Not sure what to close it as so I'll leave that to you :) Thanks

Comment 4 Fedora Update System 2010-01-19 19:33:19 UTC
iotop-0.4-1.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 5 Fedora Update System 2010-01-19 19:37:42 UTC
iotop-0.4-1.fc11 has been pushed to the Fedora 11 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.