bug-parted
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[ parted-Bugs-303476 ] parted goes into endless loop printing "You have


From: noreply
Subject: [ parted-Bugs-303476 ] parted goes into endless loop printing "You have found bug" endlessly on any command
Date: Fri, 02 Jun 2006 05:43:58 +0000

Bugs item #303476, was opened at 2006-05-25 18:40
You can respond by visiting: 
http://alioth.debian.org/tracker/?func=detail&atid=410685&aid=303476&group_id=30287

Category: parted
Group: Version 1.7.0
Status: Pending
Resolution: None
Priority: 7
Submitted By: Nobody (None)
Assigned to: Leslie P. Polzer (dejari-guest)
Summary: parted goes into endless loop printing "You have found bug" endlessly 
on any command

Initial Comment:
Invoked parded with:
> parted /dev/sda
then typed
(parted) print all

and it went into endless loop printing on screen message:
---
You found a bug in GNU Parted! Here's what you have to do:

Don't panic! The bug has most likely not affected any of your data.
Help us to fix this bug by doing the following:

Check whether the bug has already been fixed by checking
the last version of GNU Parted that you can find at:

        http://ftp.gnu.org/gnu/parted/

Please check this version prior to bug reporting.

If this has not been fixed yet or if you don't know how to check,
please visit the GNU Parted website:

        http://www.gnu.org/software/parted

for further information.

Your report should contain the version of this release (1.7.0)
along with the error message below, the output of

        parted DEVICE unit co print unit s print

and additional information about your setup you consider important.

Error: SEGV_MAPERR (Address not mapped to object)

---
command mentioned in reporting bug
> parted /dev/DEVICE print unit s print unit chs print
results in same exact behavior (DEVICE changed to sda)

results of fdisk commands:
---
> fdisk -l /dev/sda

Disk /dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1        2611    20972826    c  W95 FAT32 (LBA)
/dev/sda2            2612       30401   223223175    f  W95 Ext'd (LBA)
/dev/sda5            2612        5222    20972826    b  W95 FAT32
/dev/sda6            5223        8209    23993046    b  W95 FAT32
/dev/sda7            8210        8272      506016   82  Linux swap / Solaris
/dev/sda8            8273       10820    20466778+   b  W95 FAT32
/dev/sda9           10821       13311    20008926   83  Linux
/dev/sda10          13312       15179    15004678+  83  Linux
/dev/sda11          15180       17047    15004678+  83  Linux
> fdisk -l -u /dev/sda

Disk /dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
Units = sectors of 1 * 512 = 512 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1              63    41945714    20972826    c  W95 FAT32 (LBA)
/dev/sda2        41945715   488392064   223223175    f  W95 Ext'd (LBA)
/dev/sda5        41945778    83891429    20972826    b  W95 FAT32
/dev/sda6        83891493   131877584    23993046    b  W95 FAT32
/dev/sda7       131877648   132889679      506016   82  Linux swap / Solaris
/dev/sda8       132889743   173823299    20466778+   b  W95 FAT32
/dev/sda9       173823363   213841214    20008926   83  Linux
/dev/sda10      213841278   243850634    15004678+  83  Linux
/dev/sda11      243850698   273860054    15004678+  83  Linux
---

Interesting is that any disk releated operation results in such behavior, even 
regardless of drive (either hda or sda in my case), also parted can be closed 
only using kill -9.


----------------------------------------------------------------------

Comment By: Nobody (None)
Date: 2006-06-02 05:43

Message:
Logged In: NO 

Oh, and also, I installed 1.7.1 ... the endless loop is no more, but the 
segfault is still there, with the same backtrace.

----------------------------------------------------------------------

Comment By: Nobody (None)
Date: 2006-06-02 05:27

Message:
Logged In: NO 

Oops, sorry, I forgot the last command, here it is :
---
(gdb) bt full
#0  0xb7f43a84 in hfsc_can_use_geom () from /usr/lib/libparted-1.7.so.0
No symbol table info available.
#1  0xb7f92400 in _dl_runtime_resolve () from /lib/ld-linux.so.2
No symbol table info available.
#2  0xb7f44264 in hfsx_probe () from /usr/lib/libparted-1.7.so.0
No symbol table info available.
#3  0x0806ad1c in ?? ()
No symbol table info available.
#4  0x00000000 in ?? ()
No symbol table info available.
---

----------------------------------------------------------------------

Comment By: Nobody (None)
Date: 2006-06-02 05:25

Message:
Logged In: NO 

Hi, I have the same probelm. I did the operation you mentioned, and here is the 
output :

---
address@hidden ~ $ sudo gdb -ex run --args parted /dev/block/harddisk print
GNU gdb 6.4
Copyright 2005 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu"...(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".

Starting program: /usr/sbin/parted /dev/block/harddisk print
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)

Program received signal SIGSEGV, Segmentation fault.
0xb7f43a84 in hfsc_can_use_geom () from /usr/lib/libparted-1.7.so.0
(gdb) 
---

----------------------------------------------------------------------

Comment By: Leslie P. Polzer (dejari-guest)
Date: 2006-05-26 09:54

Message:
Logged In: YES 
user_id=12119

Thanks for the report.

The endless loop issue should be fixed for 1.7.1.

As for the rest, I cannot reproduce the bug.  Can you provide a GDB backtrace?

gdb -ex run --args parted /dev/sda
[...proceed until SIGSEGV occurs...]
Program received SIGSEGV.
(gdb) bt full
[send output to us]
(gdb) quit


----------------------------------------------------------------------

You can respond by visiting: 
http://alioth.debian.org/tracker/?func=detail&atid=410685&aid=303476&group_id=30287




reply via email to

[Prev in Thread] Current Thread [Next in Thread]