So, correction. It wasn't Nitai at all. Nitish Pandey sent me the edited debugger. That's what I get for not checking.
On Friday, March 3, 2017 at 8:07:16 AM UTC-6, Aaron J. White wrote: > > Hi guys, > > Yeah, I'm not sure why, but around the time OpenBD moved to version 3.0 > the debugger stopped working and the OpenBD team kind of started to pretend > it wasn't functionality they used to boast as a feature. No explanation was > given at all really and post about it like this were ignored. It's still > not 100%, but Nitai from Razuna was able to make some fixes to get it > running and was nice enough to send it to me. > > You can download Nitai's updated version of the OpenBD debugger here: > > https://drive.google.com/file/d/0B6rp_A0Y9Yo2LVZnbU52a3NMeXc/view?usp=sharing > > Unzip the file and add the openbddebugger folder to your project. > Obviously never include the opendbdebugger directory in a production > environment. > Below are Nitai's instructions: > To start the debugger one must call the URL with a GET parameter > start_debugger=true > and to stop it one should use the GET parameter > stop_debugger=true > Actually the variable is necessary. The value does not matter. > > > On Tuesday, February 21, 2017 at 4:01:37 AM UTC-6, Frank Werner wrote: >> >> Hello, >> >> I asked a few years ago but didn't get an answer: >> >> Can I use a debugger with OpenBD? >> >> FW >> >> -- -- online documentation: http://openbd.org/manual/ http://groups.google.com/group/openbd?hl=en --- You received this message because you are subscribed to the Google Groups "Open BlueDragon" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
