libcdio-devel
[Top][All Lists]
Advanced

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

Re: [Libcdio-devel] libcdio tools cannot read multi-exent files with Jol


From: Thomas Schmitt
Subject: Re: [Libcdio-devel] libcdio tools cannot read multi-exent files with Joliet exensions on
Date: Sat, 25 Jun 2022 12:05:49 +0200

Hi,

i pushed a new branch "joliet_multi_extent" with a single commit

  Bug fix: Recognition of multi-extent files was broken if Joliet is present
  
http://git.savannah.gnu.org/cgit/libcdio.git/commit/?h=joliet_multi_extent&id=4c840665c6d9cf2ff1cf0cd12f91b25030776c74

A new function _iso9660_recname_to_cstring() implements the conversion
which _iso9660_dir_to_statbuf() now needs at three occasions.
It can allocate the memory for the result string or put it into a
submitted memory area. (I doubt that both modes together make sense.)

A cosmetic change was to equip the recognition of "." and ".." with
curly brackets so that i could replace
  else if (u_joliet_level) {
by
  } else {

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

I began to explore the
  "Bad directory information for isolinux"
problem, which Pete Batard reported.

The commited code lets iso-info report properly and without warning the
content of Gentoo's livegui-amd64-20220605T170549Z.iso

I then took my provisory fix of yesterday and blocked the recognition
of u_joliet_level in both new occasions.
This yielded an endless stream of "." and ".." filenames. Not what Pete
reported.

But if i only disable one of the two new Joliet name recognitions, i get
the "Bad directory information for isolinux" message and a similar one
about directory "/snapshots". It does not matter which of the two i keep
disabled.
The same happens if i checkout branch "master" and compile it.

So i looks like i fixed this too, but without fully understanding what
was wrong initially.


Have a nice day :)

Thomas




reply via email to

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