Skip to content
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

Python Exception <class 'RuntimeError'>: No session started #1104

Closed
1 task done
bb33bb opened this issue May 15, 2024 · 5 comments
Closed
1 task done

Python Exception <class 'RuntimeError'>: No session started #1104

bb33bb opened this issue May 15, 2024 · 5 comments

Comments

@bb33bb
Copy link

bb33bb commented May 15, 2024

GEF+GDB version

all the same version to issue 1102

Describe the issue you encountered

image

Do you read the docs and look at previously closed issues/PRs for similar cases?

No

Architecture impacted

  • ARM64

Describe your issue. Without a proper reproduction step-by-step, your issue will be ignored.

echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope

Provide a step-by-step to reproduce your issue.

start qemu
gdb-multiarch
-ex "set confirm off"
-ex "set print pretty on"
-ex "target remote localhost:1234"
-ex "set auto-load safe-path /"

Minimalist test case

Additional context?

  • Screenshots
  • Callstack
  • Coredumps
  • If possible and useful, please upload the binary
@bb33bb
Copy link
Author

bb33bb commented May 15, 2024

if u can not reproduce, plz wait for my several trys.

I will update it .

@hugsy
Copy link
Owner

hugsy commented May 15, 2024

Yes, I cannot reproduce. Provide a more detailed step by step

Also

-ex "target remote localhost:1234"

Use gef-remote, see the docs

@bb33bb
Copy link
Author

bb33bb commented May 16, 2024

as u told me ,i use gef-remote

Env:

uname -a  
Linux singapore 6.9.0-1-MANJARO #1 SMP PREEMPT_DYNAMIC Mon May 13 07:01:28 UTC 2024 x86_64 GNU/Linux

gdb command:

echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope
gdb-multiarch \
-ex "set confirm off" \
-ex "set print pretty on" \
-ex "gef-remote localhost 1234" \
-ex "set auto-load safe-path /" \
-ex "file /run/media/xxxxx/9e4b17d7-a9ed-4cee-90f7-e8b4e511c8c1/u22docker/kernel5.10/common/vmlinux"

0

GNU gdb (GDB) 14.2
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word".
GEF for linux ready, type `gef' to start, `gef config' to configure
88 commands loaded and 5 functions added for GDB 14.2 in 0.00ms using Python engine 3.12
warning: No executable has been specified and target does not support
determining executable automatically.  Try using the "file" command.
0xffff800008e0ab6c in ?? ()
[!] Command 'gef-remote' failed to execute properly, reason: No session started
Reading symbols from /run/media/......

I am debuging qemu which is runing arm64 kernel
this time it is different from the last time's output
but as u can see, there maybe some thing not very ok.
any work if needed to reproduce, i will try my best
if this issue designed just as it is in the above, plz ignore it.

if i use

if i use target remote localhost:1234
[!] Command 'context' failed to execute properly, reason: 
Python Exception <class 'RuntimeError'>: No session started
Error while executing Python code.
Reading symbols from /run/media/avboy/9e4b17d7-a9ed-4cee-90f7-e8b4e511c8c1/u22docker/kernel5.10/common/vmlinux...
(remote) gef➤  

@hugsy
Copy link
Owner

hugsy commented May 16, 2024

I still cannot reproduce. I just re-tested it following the docs and it works as expected.

@bb33bb bb33bb closed this as completed May 17, 2024
@bb33bb
Copy link
Author

bb33bb commented May 17, 2024

I still cannot reproduce. I just re-tested it following the docs and it works as expected.

I close it now , and if find time to reproduce it. I will reopen, Thanks !!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants