Otavio Salvador <[EMAIL PROTECTED]> writes:
> At line 16, the code changes new_disk->update_mode and then try to
> walk through the partition table on the disk. Line 20 then fail and
> make the code goes out without reverting the update_mode change. This
> makes the exception to be raised later on ped_disk_destroy since it
> checks this value and abort.
>
> Does someone has any tip why this specific label is failing while the
> others are not?
Well, line 20 (_add_duplicate_part) will later call
ped_disk_add_partition as you can check on the bellow backtrace:
#0 ped_disk_add_partition (disk=0x8051310, part=0x8051708,
constraint=0x8050518) at disk.c:1757
#1 0xb7f0fc09 in _add_duplicate_part (disk=0x8051310, old_part=0x80517d0) at
disk.c:237
#2 0xb7f0fdf6 in ped_disk_duplicate (old_disk=0x80512f0) at disk.c:275
#3 0x0804a482 in test_clone_label (_i=0) at label.c:74
#4 0x0804c66e in srunner_run_all ()
#5 0x0804a655 in main () at label.c:110
It then raises an exception of overlaping partitions. This then return
0 and goes on cascate until returning without getting back to
update_mode 0.
Looks like the overlaping is the root cause of the problem. Dunno why
yet.
--
O T A V I O S A L V A D O R
---------------------------------------------
E-mail: [EMAIL PROTECTED] UIN: 5906116
GNU/Linux User: 239058 GPG ID: 49A5F855
Home Page: http://otavio.ossystems.com.br
---------------------------------------------
"Microsoft sells you Windows ... Linux gives
you the whole house."
_______________________________________________
parted-devel mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/parted-devel
