Changes between Version 5 and Version 6 of Ticket #115, comment 4


Ignore:
Timestamp:
May 16, 2019, 11:25:32 AM (5 years ago)
Author:
D Gowers

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #115, comment 4

    v5 v6  
    11To re-summarize, I tried 4 different things:
    2  * Case 1: ./bin/grafx-sdl, invoked from the root of the git clone : Works
    3  * Case 2: grafx2-sdl or /usr/local/bin/grafx2-sdl : Crashes (SIGSEGV)
     2
     3 * Case 1: grafx2-sdl or /usr/local/bin/grafx2-sdl : Crashes (SIGSEGV)
     4 * Case 2: ./bin/grafx-sdl, invoked from the root of the git clone : Works
    45 * Case 3: gdb grafx2-sdl or gdb /usr/local/bin/grafx2-sdl : Works
    56 * Case 4: /tmp/g/grafx2-sdl, after setting up as described above : Works
    67
    7 Invoking with the -v option does not give ''any'' debug output in case 2. Presumably this is because the crash occurs before any output is given. In fact, your own log shows evidence of this fact: the error about the missing PNG is the first message. As I stated above, this PNG error does not show for case 2, implying that the crash occurs before this check for the PNG is made.
     8Result of invoking with -v option
     9 * Case 1 : No output with -v. No output without -v.
     10 * Case 2,3,4 : Some console output, as shown below.
    811
    9 (I admit that there is a possible alternative hypothesis here: The crash is interfering with the console output so that the check for the PNG still occurs but the error message does not show. However, I consider this possibility to be unlikely.)
     12To reiterate that, invoking with the -v option does not give ''any'' output in case 2 (debug or otherwise). Presumably this is because the crash occurs before any attempt to output a debug message is made. Notice how in your output sample, the error about the missing PNG is the first message?  As I stated in my earlier message, this PNG error does not show for case 2, implying that the crash occurs before this check for the PNG is made.
    1013
    11 Case 1 and 4 give pretty normal looking debug output when run with -v.
    12 I'll try using -v with case 3, but I expect it to produce the same output as 1 and 4 do.
     14(I admit that there is a possible alternative explanation here: The crash is interfering with the console output so that the check for the PNG still occurs but the error message does not show. However, I consider this possibility to be unlikely.)
    1315
    14 EDIT:
    15 Yes, case 3 gives the same output as case 1 and 4 do. Here is some sample output:
     16Case 2, 3, 4 give pretty normal looking debug output when run with -v.
     17
     18EDIT: Here is some sample output, from case 3:
    1619
    1720----