-
Notifications
You must be signed in to change notification settings - Fork 124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
\dkr no longer shows the crash log #191
Comments
Maybe related to my latest commits with the null command?
… On 30 Aug 2019, at 12:26, Grant Douglas ***@***.***> wrote:
When attempting to get the crash report after failing, \dkr simply returns error: Script is destroyed
Looking into this and will PR
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Probably yes, working as of 723267b |
Yep - narrowed it down to 7097e37 |
Nasty/lazy fix because I'm about to be AFK all day today but you can probably think of a better way than I can anyway :) |
Send pr and use ! Instead of ==0
… On 1 Sep 2019, at 13:32, hexploitable ***@***.***> wrote:
if (result) {
json_object_unref (result);
}
else if (strncmp (command, "dkr", 3) == 0) { //compensate for dkr
//pass
}
else
{
return NULL;
}
Nasty/lazy fix because I'm about to be AFK all day today but you can probably think of a better way than I can anyway :)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When attempting to get the crash report after failing,
\dkr
simply returnserror: Script is destroyed
Looking into this and will PR
The text was updated successfully, but these errors were encountered: