-
Notifications
You must be signed in to change notification settings - Fork 279
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
Is this gdb
functionality supposed to work?
#31
Comments
----- Original Message -----
I know i'm able to define macros in `~/.gdbinit` (just not interactively
using `define` from the `crash` prompt)
hoping to have a string comparison in such a macro using `$_streq` as per
https://sourceware.org/gdb/onlinedocs/gdb/Convenience-Funs.html
When I have the test macro
```
define dotest
if $_streq("1", "1")
echo ok\n
end
end
```
I observe different results between `gdb` and `crash`
```
(gdb) dotest
ok
```
vs
```
crash> dotest
You can't do that without a process to debug.
gdb: gdb request failed: dotest
Apparently not. As the error message states, you can't do it
"without a process to debug". And when the crash utility uses gdb,
it brings it up as "gdb vmlinux", so there is no concept of a process.
Dave
…
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
#31
|
but the |
----- Original Message -----
but the `gdb` test I tested with was not attached to a running process either
(launched just as `$ gdb`)
Yeah, hmmm, then I don't know what the issue is. I've never tried
to use a gdb macro from within crash before.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I know i'm able to define macros in
~/.gdbinit
(just not interactively usingdefine
from thecrash
prompt)hoping to have a string comparison in such a macro using
$_streq
as per https://sourceware.org/gdb/onlinedocs/gdb/Convenience-Funs.htmlWhen I have the test macro
I observe different results between
gdb
andcrash
vs
The text was updated successfully, but these errors were encountered: