Quick Links: Download Gideros Studio | Gideros Documentation | Gideros community chat | DONATE
Can't Debug Exported Project - Page 2 — Gideros Forum
  • Home
    • ›

    Can't Debug Exported Project

    2»

    Comments

    • hgy29hgy29 Maintainer
      @keszegh, yes, that's pretty much the issue I have too, detecting that the player was closed either by the user or by ZBS. I guess it should be possible to check if the process is still running with its pid
      +1 -1Share on Facebook
    • keszeghkeszegh Member
      sometimes zbs crashes with the following error:
      Longtitle Productions, creator of
      Fragmenter - animated loop machine and IKONOMIKON - the memory game
      +1 -1Share on Facebook
    • hgy29hgy29 Maintainer
      @keszegh, that's more a ZBS issue than Gideros
      +1 -1Share on Facebook
    • keszeghkeszegh Member
      edited January 2024
      ok, what about these?:
      keszegh said:

      my issues with my project came from the fact that mobdebug was not in the root folder. if it is in some subfolder then how should i require it?

      also, a print right after requiring mobdebug is not printed but if i put it later enough then it does. what does this depend on? can you make every print printed?

      finally, after quitting the player, every print is repeated once again (with those prints appearing too which were not appearing (as being too close to require for example). can you make it that this does not happen?

      Longtitle Productions, creator of
      Fragmenter - animated loop machine and IKONOMIKON - the memory game
      +1 -1Share on Facebook
    • keszeghkeszegh Member
      hgy29 said:

      @keszegh, that's more a ZBS issue than Gideros

      in the past this never happened so i assumed it is somewhat related to the new implementation of debugging.
      Longtitle Productions, creator of
      Fragmenter - animated loop machine and IKONOMIKON - the memory game
      +1 -1Share on Facebook
    • hgy29hgy29 Maintainer
      keszegh said:

      my issues with my project came from the fact that mobdebug was not in the root folder. if it is in some subfolder then how should i require it?

      Can't you just include the subfolder in the require command, that is require 'subfolder/mobdebug' ?
      keszegh said:

      also, a print right after requiring mobdebug is not printed but if i put it later enough then it does. what does this depend on? can you make every print printed?

      finally, after quitting the player, every print is repeated once again (with those prints appearing too which were not appearing (as being too close to require for example). can you make it that this does not happen?

      Not sure how ZBS fetches gideros logs. Did you try my improved gideros interpreter for ZBS (GiderosLink, https://forum.gideros.rocks/discussion/comment/68714 #Comment_68714) ?
      Meanwhile I improved quit/disconnect handling.
      +1 -1Share on Facebook
    • keszeghkeszegh Member
      Can't you just include the subfolder in the require command, that is require 'subfolder/mobdebug' ?
      - this did not seem to work for me

      Did you try my improved gideros interpreter for ZBS (GiderosLink)
      - I have overlooked this. now i will check it out, thanks.
      Longtitle Productions, creator of
      Fragmenter - animated loop machine and IKONOMIKON - the memory game
      +1 -1Share on Facebook
    • keszeghkeszegh Member
      @hgy29, when using GiderosLink interpreter, ZBS crashes always with this message:
      Longtitle Productions, creator of
      Fragmenter - animated loop machine and IKONOMIKON - the memory game
      +1 -1Share on Facebook
    • hgy29hgy29 Maintainer
      Yep, it looks like ZBS 2.0 version has changed something, but the fix is easy, change first line of gideros_protocol.lua into:
      local socket=require "socket.core"
      +1 -1Share on Facebook
    • hgy29hgy29 Maintainer
      keszegh said:

      Can't you just include the subfolder in the require command, that is require 'subfolder/mobdebug' ?
      - this did not seem to work for me
      I just tried and it works for me, is your mobdebug.lua correctly referenced in gideros project file ?

      +1 -1Share on Facebook
    • keszeghkeszegh Member
      hgy29 said:

      Yep, it looks like ZBS 2.0 version has changed something, but the fix is easy, change first line of gideros_protocol.lua into:

      local socket=require "socket.core"
      it still does not work. zbs does not crash anymore but also the app is not started in the player.
      Longtitle Productions, creator of
      Fragmenter - animated loop machine and IKONOMIKON - the memory game
      +1 -1Share on Facebook
    • keszeghkeszegh Member
      hgy29 said:

      keszegh said:

      Can't you just include the subfolder in the require command, that is require 'subfolder/mobdebug' ?
      - this did not seem to work for me
      I just tried and it works for me, is your mobdebug.lua correctly referenced in gideros project file ?

      ok, i will check, in any case putting in root works for now.
      Longtitle Productions, creator of
      Fragmenter - animated loop machine and IKONOMIKON - the memory game
      +1 -1Share on Facebook
    • hgy29hgy29 Maintainer
      keszegh said:


      it still does not work. zbs does not crash anymore but also the app is not started in the player.

      It works for me with latest ZBS, but you also need latest Gideros since it requires an updated bridge/daemon to work

      +1 -1Share on Facebook
    • keszeghkeszegh Member
      hgy29 said:

      keszegh said:


      it still does not work. zbs does not crash anymore but also the app is not started in the player.

      It works for me with latest ZBS, but you also need latest Gideros since it requires an updated bridge/daemon to work

      i see, sounds good. for now i'm stuck with 2023.9.1 due to imgui rendering issues mentioned in the other thread. hopefully those will be sorted out and then i'm back to the latest version.
      Longtitle Productions, creator of
      Fragmenter - animated loop machine and IKONOMIKON - the memory game
      +1 -1Share on Facebook
    • keszeghkeszegh Member
      the gideroslink you said works nicely, it seems that now i don't need to kill the gdrdaemon task manually anymore. i have to stop debugging with shift-f5 manually though after i quit the player.
      Longtitle Productions, creator of
      Fragmenter - animated loop machine and IKONOMIKON - the memory game
      +1 -1Share on Facebook
    • troysandaltroysandal Member
      I just hit a breakpoint in my Gideros project, THANK YOU!!!!!

      Likes: MoKaLux, keszegh

      +1 -1 (+2 / -0 )Share on Facebook
    • keszeghkeszegh Member
      i've noticed that the performance when debugging (that is when i start the code with mobd=require('mobdebug').start("192.168.0.164")) is really bad, my app starts to lag quickly. even if i do nothing with debugging (no prints, no breakpoints). could this performance somehow improved? i do not seem to recall that in the lua days debugging slowed down the player this much.
      without debugging it is good.

      also in gideros ide where it is theoretically debugging too, it runs fast. even with many prints. btw how can i add breakpoints in gideros ide? i seem to remember that it was possible but i can't find how.
      Longtitle Productions, creator of
      Fragmenter - animated loop machine and IKONOMIKON - the memory game
      +1 -1Share on Facebook
    • hgy29hgy29 Maintainer
      I am afraid that enabling mobdebug automatically enable debugging hooks, which means that some extra code will be run after each lua instruction to check if line was changed or a breakpoint was hit. I can review the coded added for mobdebug compatibilty, to see if things can be improved.

      When Gideros IDE is in charge of debugging, those hooks are enabled too but handled directly in C code, instead of relying on lua hooks. Maybe this is why mobdebug is slower currently.

      To set a breakpoint in Gideros Studio, just click at the beginning of the line number column, to the left of the line number.

      Likes: MoKaLux, keszegh

      +1 -1 (+2 / -0 )Share on Facebook
    • keszeghkeszegh Member
      ah, i did click at the beginning of the line but not left enough. there should be some menu item too for adding/removing breakpoints though.

      yes, probably lua is way slower than c in this sense, when i'm running for cycles on each frame on multiple arrays that have size>1000. i don't know what you can do but anything is appreciated. at least if i'm right and past zbs debugging was faster, then there must be some way to make the slowdown more reasonable. thanks a lot.

      Likes: MoKaLux

      Longtitle Productions, creator of
      Fragmenter - animated loop machine and IKONOMIKON - the memory game
      +1 -1 (+1 / -0 )Share on Facebook
    • hgy29hgy29 Maintainer
      keszegh said:


      yes, probably lua is way slower than c in this sense, when i'm running for cycles on each frame on multiple arrays that have size>1000. i don't know what you can do but anything is appreciated. at least if i'm right and past zbs debugging was faster, then there must be some way to make the slowdown more reasonable. thanks a lot.

      I had a second look at the code, and I don't think it can be made significantly faster. We could probably optimize a few calls, but I doubt this will make a big difference.
      +1 -1Share on Facebook
    • keszeghkeszegh Member
      @hgy29 , thanks for looking. it is a bit bad as i need to turn on/off debugging depending on if i want to really debug something specifically, as otherwise it is too slow to test the app itself. but still way better than having no debugging at all, so thanks for your recent efforts in this direction.

      Likes: MoKaLux

      Longtitle Productions, creator of
      Fragmenter - animated loop machine and IKONOMIKON - the memory game
      +1 -1 (+1 / -0 )Share on Facebook
    Sign In or Register to comment.