search

kometbomb / klystrack

A chiptune tracker
http://kometbomb.github.io/klystrack/
Other
481 stars 29 forks source link

Crash on launch with GDB 6.8, Klystrack 1.50 r638 #24

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
In commandline, run "C:\...\gdb C:\...\klystrack.exe"

What is the expected output? What do you see instead?

GDB launches, typing "run" executes Klystrack, and GDB starts recording events. 
 What happens instead is I get a segmentation fault.

What version of the product are you using? On what operating system?
I was using 1.50 r638 in Windows Vista Home Premium SP2, with GDB 6.8 (is there 
a more recent version I should use? it came with MinGW's latest release)
Please provide any additional information below.

I was trying to report another issue involving specific instrument parameters, 
actually, when this happened.  It crashed when playing back the instrument in 
the Instrument Editor and when I tried to save the same instrument to have an 
example of the problem.  Beyond these issues, it all works without problems.

Output on crash (just attempting to run under GDB):

Program received signal SIGSEGV, Segmentation fault.
0x00408e02 in ?? ()

GDB output (bt):

#0  0x00408e02 in ?? ()
#1  0x00000000 in ?? ()

Original issue reported on code.google.com by arinla...@gmail.com on 6 Jul 2010 at 5:03

GoogleCodeExporter commented 9 years ago 
Does this happen every time? Can you somehow work out the exact line numbers 
yourself since the address doesn't point to any suspicious line (I see 
export.c:108)? 

 I.e.   addr2line -e bin.debug/klystrack.exe 0x00408e02

Original comment by kometb...@gmail.com on 6 Jul 2010 at 1:11

GoogleCodeExporter commented 9 years ago 
I think I might have done something wrong, but can't put my finger on it, as 
they look rather unhelpful.

C:\Users\family>C:\MinGW\bin\addr2line.exe -e 
Desktop\Trackers\Klystrack\klystrack.exe 0x00408e02
??:0

C:\Users\family>C:\MinGW\bin\addr2line.exe -e 
Desktop\Trackers\Klystrack\klystrack.exe 0x00000000
??:0

Original comment by arinla...@gmail.com on 12 Jul 2010 at 7:50

GoogleCodeExporter commented 9 years ago 
Looks weird. It looks like there are no symbols in the binary... are you sure 
you are compiling the binaries in debug mode? 

Also, have you tried with the latest nightly? There was something that made the 
app crash if the working directory was not the same as where klystrack.exe is 
located (on Windows).

Original comment by kometb...@gmail.com on 12 Jul 2010 at 12:47

GoogleCodeExporter commented 9 years ago 
I'm using the available downloads because I can't seem to compile in Windows, 
or find out why I can't.

Original comment by arinla...@gmail.com on 14 Jul 2010 at 7:35

GoogleCodeExporter commented 9 years ago 
Ah ok, that makes sense. I'll start including the debug exec in the nightly 
archive, use that in the future. :) It has all that information that tells GDB 
where the program is crashing.

Original comment by classicl...@gmail.com on 14 Jul 2010 at 10:56