Instrument editor causes crash in Vista about klystrack

[GoogleCodeExporter]

Did you forget to attach a screenshot? 

Original comment by [email protected] on 18 May 2010 at 12:25

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Sorry about that, I didn't forget it, I deleted the image and didn't edit the 
post
(don't know how).  I'll stick the image to this comment.

Something I didn't look into is that the program only crashes when I have the 
window
maximized and do the above procedure.

Original comment by [email protected] on 18 May 2010 at 10:11

Attachments:

• klystrack.png

[GoogleCodeExporter]

I was unable to reproduce this. I think the only option left is that you 
install 
MinGW, compile the debug build and try reproducing the crash under gdb.

Original comment by [email protected] on 1 Jun 2010 at 10:47

• Changed state: Accepted
• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

I ran mingw32-make v3.82, and got the following error, despite it building 
properly
in Linux, and am unsure how to proceed:

C:\Users\family\Desktop\Arin'sstuff\SVN\klystrack>"C:\MinGW\bin\mingw32-make.exe
"
-n '#define VERSION "' >> src/version_number.h
'"' >> src/version_number.h
-n '#define REVISION "r' >> ./src/version.h
'"' >> ./src/version.h
'make' is not recognized as an internal or external command,
operable program or batch file.
mingw32-make: *** [build] Error 1

Original comment by [email protected] on 2 Jun 2010 at 6:35

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I couldn't build from source (last comment, probably my own fault, as I've never
compiled anything but a few lines of C in Windows), and got a readout from the 
bug
occuring in r587.  Here's hoping it can help you out.

Original comment by [email protected] on 3 Jun 2010 at 5:59

Attachments:

• klystrackgdbvista.txt

[GoogleCodeExporter]

Excellent, much appreciated. I'll get on it asap.

Original comment by [email protected] on 3 Jun 2010 at 2:05

[GoogleCodeExporter]

Oh btw, it would make this even easier to debug if you could type in "bt" after 
that
crash at 0x00000000 (bt shows the function call history; in other words, the 
exact
line where the crash happened.)

Original comment by [email protected] on 3 Jun 2010 at 2:06

[GoogleCodeExporter]

Here you go:

#0  0x00000000 in ?? ()
#1  0x0040bc7b in ?? ()
#2  0x00b9be98 in ?? ()
#3  0x0024ac88 in ?? ()
#4  0x0024ac74 in ?? ()
#5  0x00000000 in ?? ()

Original comment by [email protected] on 3 Jun 2010 at 9:23

[GoogleCodeExporter]

Ok, please check the latest nightly. I forgot to add some descriptions for the 
instrument editor parameters which have been missing since 1.4 and caused a 
crash very randomly.

Original comment by [email protected] on 16 Jun 2010 at 7:44

• Changed state: Started
• Added labels: OpSys-All

[GoogleCodeExporter]

It's still crashing for me, same error as above.

I just read all the posts, and realized I should mention that it only happens 
at pixel size 2 in Vista.  I'm sorry for not mentioning that sooner.

Original comment by [email protected] on 17 Jun 2010 at 7:27

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

The nightly build of 1.5 (r638), does not have this bug, and is visually 
stunning.

Original comment by [email protected] on 4 Jul 2010 at 4:58

[GoogleCodeExporter]

Ok, great. I'll close this for now but since I didn't intentionally fix this, 
keep an eye on it.

Original comment by [email protected] on 4 Jul 2010 at 3:40

• Changed state: Verified