Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gui is not runnning #1

Open
gasilva opened this issue Jan 31, 2013 · 3 comments
Open

Gui is not runnning #1

gasilva opened this issue Jan 31, 2013 · 3 comments
Assignees

Comments

@gasilva
Copy link

gasilva commented Jan 31, 2013

I have a dual socket Xeon sandy-bridge. The i7z is work but not the GUI. Both compiled with no errors. I already installed msrtools and msr-tools in ubuntu 12.10. Could you give me some light on this issue?

i7z DEBUG: i7z version: svn-r77-(20-Nov-2011)
i7z DEBUG: Found Intel Processor
i7z DEBUG:    Stepping 7
i7z DEBUG:    Model d
i7z DEBUG:    Family 6
i7z DEBUG:    Processor Type 0
i7z DEBUG:    Extended Model 2
i7z DEBUG: msr = Model Specific Register
i7z DEBUG: Detected an i7 - 32nm (haven't seen this version around, do write to me with the model number)
i7z DEBUG: msr device files exist /dev/cpu/*/msr
i7z DEBUG: You have write permissions to msr device files
@ghost ghost assigned ajaiantilal Feb 1, 2013
@ajaiantilal
Copy link
Owner

hello

am i correct to assume that the console version works (the ncurses gui), and not the Qt-based GUI version.

can you paste the entire output that you get?

@gasilva
Copy link
Author

gasilva commented Feb 1, 2013

Yes. The text-based version is working OK. I just dropped this note to inform you about that.

I compiled and ran the code in an i7 and both text and GUI versions worked in Ubuntu 12.04. The GUI did not work in a Xeon with Ubuntu 12.10.

The code lines above are all the output I got after the crash.

@ajaiantilal
Copy link
Owner

thanks a lot for the bug report.

yeh, the qt code has some major issues going on. some combination like using optimization flags seem to crash it. i am embarrassed to say that even it doesn't display the bars correctly on my development machine :(

i am thinking of doing a major rehaul of the qttool once i get some more time to work on it (and test on multiple OS's) in maybe a couple of weeks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants