next »

[Guest]

Hi

Sometimes (not often!) XMPLAY (latest stuff+all earlier versions) just crashes on replaying .xm or it. files, esp when starting a new playlist

Any chance to add an option for kinda crash.log file to it?

So the problem can *maybe* be found + solved faster


Regards Guest

[Pike84]

There's the drwatson log of Windows for that purpose. I don't know if it'd be possible to create a useful crash log for XMP, since crashes are, well, unpredictable .

[Rah'Dick]

The DrWatson log is pretty much useless to the average user. People with debugging tools and the original source code (Ian) might find it very useful, tho.

Still, I agree - a humanly readable crashlog would make some things easier, for example finding out whether a particular file crashed XMPlay or whether your sound card fu**ed up...

[Ian @ un4seen]

The way I like to do things is to first see a DrWatson log entry. Often, that alone will be sufficient to see what the problem is, but if not, it will generally at least show where the problem is, and some targeted logging can then be done to find the cause. So, if you've had any crashing, please reproduce it with the latest "stuff" version, and upload the drwtsn32.log

   ftp.un4seen.com/incoming/

[Guest]

Ian, i uploaded my drwtsn32.log to your ftp

[Ian @ un4seen]

It crashed while scanning info (eg. tags) from a file; I guess you had just added a new file to the playlist/library? Unfortunately, the log doesn't show which scanner the crash occurred in; it could be one of the built-in format scanners or it could be a plugin. So to narrow it down a bit, please try to reproduce the crash after removing all the plugins, eg. put XMPLAY.EXE on its own in a directory.

[Guest]

ok i will try to reproduce just with only latest stuff xmplay.exe in the dir

but a dedicated crash.log for xmplay only would be easier:)


laters

Guest 

[saga]

it would just slow down the player and also increase its micro-size.
seriously, most people have no issues with xmplay at all so the current option (Ian builing "dedicated" debug builds) is really better.

[Guest]

I cant reproduce the crash with only xmplay in the dir and it/.xm replay 

so its one of the winamp or xmplay plugins

and i have many

Any idea that can help to trace the prob beside test each ?


Greets Guest

[saga]

instead of adding one plug by the other, you can first add half of them. if the problem occours again, you've already the buggy in this list... if not, remove the plugins and add the other half. then, divide the half that's in the xmplay folder again in two halfs, and so on...

[Rah'Dick]

instead of adding one plug by the other, you can first add half of them. if the problem occours again, you've already the buggy in this list... if not, remove the plugins and add the other half. then, divide the half that's in the xmplay folder again in two halfs, and so on...

Hehe, Quicksort for beginners

[Guest]

interesting advices:)

but maybe its a "combo" of some plugins that causes that crash and not only one
i'm using 36 winamp  + 39 xmplay plugs

... a dedicated crashlog *maybe* could make it easier and it seems dr.watson log not been helpful for trace


cheers
Guest

 


 

[saga]

Hehe, Quicksort for beginners

indeed!

... a dedicated crashlog *maybe* could make it easier and it seems dr.watson log not been helpful for trace

you can ask Ian if he can create a crash log for your case.

[Guest]

I didnt asked for a personalized version , cos other probably having problems too
and a generic log option can be used by all people.

you can ask Ian if he can create a crash log for your case.

@Ian . Can u pls add a crash-log option for me personally ?


Greets Guest

 

[Ian @ un4seen]

@Ian . Can u pls add a crash-log option for me personally ?

Yep. Please give your email address, and I'll send you a debug version to reveal which plugin is crashing.

[debug]

Ian , you have mail


regards

debug aka Guest

[Ian @ un4seen]

Ian , you have mail

So should you