openMSX post-0.7.0 build available for beta testing

Page 6/9
1 | 2 | 3 | 4 | 5 | | 7 | 8 | 9

By RyJuZo

Master (236)

RyJuZo's picture

07-06-2009, 19:24

Ok found something else..

when using a debugger(my own debugger or yours 0.1.0-dev8230) to connect to openmsx and I start stepping in/over. Openmsx quits for no reason. This happens after a random number of steps never the same amount?

and here's the very curious part it, I ran it on two laptops both running XP pro sp3.
one is my new laptop dell precision pro with 2 duo CPU T9400 @ 2.53GHZ and 4GB of ram
and the other is my older laptop also dell precision pro P4 1 CPU @ 3.0GHZ and 2GB of ram

the problem only occurs on my new laptop with all new versions of openmsx.

Do you know why openmsx quits like that, meaning is this a known issue? Is there a way to look at some verbose logging file and see what the reason could be?

Question

By RyJuZo

Master (236)

RyJuZo's picture

07-06-2009, 19:24

Ok found something else..

when using a debugger(my own debugger or yours 0.1.0-dev8230) to connect to openmsx and I start stepping in/over. Openmsx quits for no reason. This happens after a random number of steps never the same amount?

and here's the very curious part it, I ran it on two laptops both running XP pro sp3.
one is my new laptop dell precision pro with 2 duo CPU T9400 @ 2.53GHZ and 4GB of ram
and the other is my older laptop also dell precision pro P4 1 CPU @ 3.0GHZ and 2GB of ram

the problem only occurs on my new laptop with all new versions of openmsx.

Do you know why openmsx quits like that, meaning is this a known issue? Is there a way to look at some verbose logging file and see what the reason could be?

Question

By mfeingol

Champion (291)

mfeingol's picture

07-06-2009, 20:22

RyJuZo:

I can't reproduce the issue on Vista x64 with the latest SVN builds of openmsx and the debugger. Which precise versions of each are you using?

To make further progress, please try to provide a user dump of the openmsx process crash.

If you're running Windows Vista SP1, you can find user dump files for crashed processes in the "%LocalAppData%\CrashDumps" directory. The default Windows crash dump behavior can be further customized as per the following article: http://msdn.microsoft.com/en-us/library/bb513638(VS.85).aspx

To generate a user dump on demand on any Windows OS, please read KB286350: http://support.microsoft.com/kb/286350

By RyJuZo

Master (236)

RyJuZo's picture

07-06-2009, 21:09

RyJuZo:
To make further progress, please try to provide a user dump of the openmsx process crash.

There is no crash...openmsx just quits with no message at all.

so NO debug info to give...

that's why I asked if it's possible to turn on some sort of logging within openmsx itself to see why it quits.

all I do is sending the command step_in/step_over thru a socket connection a couple of times

If I give this command on the openmsx-console(F10) the same couple of times then it does not quit.

I've tested this on versions 0.7.0 until the last release, all have the same issue.

btw. and I dont use Vista but XP...so I use the 32bit versions

By mfeingol

Champion (291)

mfeingol's picture

07-06-2009, 22:28

RyJuZo:

The process exiting may be a result of a crash, or some part of the program terminating itself. Either way, a crash dump should help us figure out what went wrong.

I tried to repro your scenario in XP with no luck. I used the following bits:

http://openmsx.sf.net/temp/openmsx-0.7.1-dev9895-VC-x86.msi
http://openmsx.sf.net/temp/openmsx-debugger-0.7.1-dev9782-VC-x86.zip
http://openmsx.sf.net/temp/Qt-4.4.3-x86.zip

Can you please make sure these are the binaries you're using?

After that, would it be possible for you to install the Windows debuggers package from http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx and then follow the instructions in http://support.microsoft.com/kb/286350 to monitor the openmsx.exe process for crashes?

By RyJuZo

Master (236)

RyJuZo's picture

07-06-2009, 23:31

okay...I'll get back to you with the results

By RyJuZo

Master (236)

RyJuZo's picture

08-06-2009, 00:26


http://openmsx.sf.net/temp/openmsx-debugger-0.7.1-dev9782-VC-x86.zip
http://openmsx.sf.net/temp/Qt-4.4.3-x86.zip

this debugger does not quite run, I get: "error executing program"

and the openmsx-debugger version I have does not want to connect to the new openmsx-version!?

By RyJuZo

Master (236)

RyJuZo's picture

08-06-2009, 00:44


http://openmsx.sf.net/temp/openmsx-0.7.1-dev9895-VC-x86.msi

Btw I cannot even get a succesfull connection to this version of openmsx with just plain TELNET!? Can you?
I mean the port used can still be found in the temporary-path "...\openmsx-default\socket.*" right? or does this version use a different method?

:-?

By flyguille

Prophet (3028)

flyguille's picture

08-06-2009, 02:37

I just installed OpenMSX plus catapult pack, and I am trying to do a LLIST, and to get the result in a file... so I selected the logger in catalist, but the LLIST command never ends, & no file nowhere.

What can be the problem?

EDIT :, seens that was the catapult thing.

but now ¿why you can't to preset the print output device or filename BEFORE to launch the emulator? ¿why that setup isn't saved, so is empty each time that I run catapult?

By Manuel

Ascended (18082)

Manuel's picture

08-06-2009, 09:28

RyJuZo: the new debugger runs fine here: did you put everything in the same dir? (Including the Qt libs from that 2nd zip?)

About connecting: yes, it has been changed, because the old method was insecure. It's now using SSPI on Windows. You can see in the debugger source code how that's done. This way, we make sure that only the user who started openMSX can connect to it and not someone else. (This would be rather dangerous, because he could connect and access the complete filesystem of the user... including removing all files... Luckily, multiuser PC's with Windows generally are not running openMSX often... Anyway, this will be fixed in 0.7.1, as you've noticed.)

flyguille: because this Catapult is an old app, which isn't really worked on anymore. Also, no one ever noticed this inconvenience.

Page 6/9
1 | 2 | 3 | 4 | 5 | | 7 | 8 | 9