0.2.71 release & Mac OS X/Darwin 1.3
Eric Carlson
carl0240 at tc.umn.edu
Sat Apr 14 03:29:02 CEST 2001
On Friday, April 13, 2001, at 09:49 AM, Samuel Hocevar wrote:
> On Fri, Apr 13, 2001, Eric Carlson wrote:
>
>> BTW, i'm disabling GTK above because my GTK install is a bit broken and
>> I have no use for it anyway.
>
> AFAIK, the Gtk interface hasn't been tested under OS X, please let us
> know if you ever manage to get it working.
Will do...
>
>> module: browsing //lib
>
> Ok, this should have been "./lib" instead of "//lib". My fault, it
> should be
> fixed in CVS. Try the following patch:
> <snip>
Thanks much! Command line vlc works now, but vlc.app is really touchy
with regards to the open file dialog. More specifically, when I click on
a file to open, the app frequently quits, sometimes following the system
spinning disk cursor. I'm guessing this is related to some code that
identifies if a file is OK for the app to open or not, since it has died
every time selecting the unencrypted vob file to open, dies if I
accidentally click on (but not open) a tiff file, for example, and
sometimes when i click on and try to open a supported MPEG1 file. And,
of course, thanks to something (maybe the OS?) remembering which file I
was trying to open last in that application, any subsequent attempts
fail immediately.
>> I've also messed around a bit with the unfinished DVDioctl.kext from
>> 0.2.70 with the dangerous ioctl stuff enabled. I've got kernel panic
>> output if anyone's interested.
>
> I experienced the same behaviour. I couldn't really track the problem
> because I don't have physical access to an OS X box, so if you have any
> additional information on this topic it can be useful.
OK... here's the info I have, first the kernel panic text (hand copied
from the screen of the crashed box. I double checked it all but it's
possible I may have mis-typed something):
Unresolved kernel trap(cpu 0): 0x300 Data access DSISR=0x40000000
DAR=0x0e893138 PC=0x12743c88, MSR=0x00009030
generating stack backtrace prior to panic:
backtrace: 0x12743c80 0x12743c80 0x127483b8 0x0024adb8 0x151a5b98
0x000c2cc8 0x000bfb70 0x001a621c 0x0009d1e4 0x00099440 0x00000268
0x00000000
kernel modules in backtrace: DVDioctl(1.0.0d1)@0x151a4000
com.apple.iokit.IOSCSIMultimediaCommandsDevice(1.0)@0x1273b000
kernel module dependencies:
com.apple.iokit.IOSCSIBlockCommandsDevice(1.0)@0x1270c000
com.apple.iokit.IOSCSIArchitectureModel(1.0)@0x12672000
com.apple.iokit.IOStorageFamily(1.0.0b1)@0x0
com.apple.iokit.IODVDStorageFamily(1.0.0b1)@0x0
com.apple.iokit.IOCDStorageFamily(1.0.0b1)@0x0
Memory access exception (1,0,0)
What I did that caused the panic:
vlc run as: ./vlc dvd:/dev/dvd
Sorry I didn't run it with -vvvv :-(
The DVD in the drive was The Matrix (US release)
vlc build 0.2.70, DVDioctl kernel module from that release loaded, with
source mods to enable dangerous io following instructions I found in the
list archives (either vlc-devel or vlc, I forget) from March(?).
screen output:
./vlc
./lib
intf: interface initialized
./vlc
./share
vout: video display initialized (720x576, 32/32 bpp)
vout: YUV acceleration unavailable!
<crashed here>
I connected with gdb (the remote debugger) from another machine while
that machine was still panic'd. Since I don't really have any experience
with gdb, I dug around in the help file but this is all the info I could
really get it to show (I believe this is a stack backtrace... it should
match the kernel panic output above):
(gdb) bt
#0 0x12743c88 in ?? ()
#1 0x127483b8 in ?? ()
#2 0x0024adb8 in ?? ()
#3 0x151a5b98 in ?? ()
#4 0x000c2cc8 in ?? ()
#5 0x000bfb70 in ?? ()
#6 0x001a621c in ?? ()
#7 0x0009d1e4 in ?? ()
#8 0x00099440 in ?? ()
#9 0x00000268 in ?? ()
warning: ppc_frame_chain_valid: stack pointer from 0x1231ffc0 to
0x2086450 grows upward; assuming invalid
Hardware info: PowerMac G4/500 dual (gigabit), stock DVD-RAM drive on
internal ATA bus. OS X 4K78 (xnu-123.5, according to uname -a).
I'll test any changes anyone makes to the DVDioctl.kext stuff... I've
got 2 machines here with DVD drives and OS X installed (A Powerbook and
the above G4) and another box with no dvd drive but OS X installed as
well.
> By the way, when reading unencrypted DVDs, are you reading the
> mounted VOB files, or are you reading directly from /dev/dvd using the
> DVDioctl KEXT ?
Neither... I've been testing with an unencrypted VOB file obtained using
a MacOS 9 app called DVDExtractor that reads a DVD, decrypts a vob file,
and saves it to disk (necessary since I don't own any unencrypted DVDs).
I've been getting around 18-22 fps playing that VOB file off my hard
drive using the command line vlc program.
Hope that helps.
Eric
More information about the vlc-devel
mailing list