Could NOT attach to process
See original GitHub issueI want to attach a shared library (.so) file to a running process.
my launch.json
file reads,
{
"type": "gdb",
"request": "attach",
"name": "Attach to PID",
"target": "14823",
"cwd": "${workspaceRoot}",
"valuesFormatting": "parseText"
},
The output from the debug console,
[Inferior 1 (process 18766) detached]
Warning: 'set target-async', an alias for the command 'set mi-async', is deprecated.
Use 'set mi-async'.
[New LWP 18769]
[New LWP 18770]
[New LWP 18771]
[New LWP 18772]
[New LWP 18774]
[New LWP 18775]
[New LWP 18776]
[New LWP 18777]
[New LWP 18781]
[New LWP 18782]
[New LWP 18784]
[New LWP 18786]
[New LWP 18792]
[New LWP 18793]
[New LWP 18794]
[New LWP 18795]
[New LWP 18796]
[New LWP 18797]
[New LWP 18798]
[New LWP 18799]
[New LWP 18800]
[New LWP 18801]
[New LWP 18803]
[New LWP 18804]
[New LWP 18805]
[New LWP 18810]
[New LWP 18811]
[New LWP 18812]
[New LWP 18813]
[New LWP 18816]
[New LWP 18819]
[New LWP 18820]
[New LWP 18821]
[New LWP 18822]
warning: Could not load shared library symbols for bin/linux64/launcher_client.so.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x00007f7a856bd868 in __GI___clock_nanosleep (clock_id=clock_id@entry=0, flags=flags@entry=0, req=0x7ffea540f510, rem=0x7ffea540f500) at ../sysdeps/unix/sysv/linux/clock_nanosleep.c:78
78 ../sysdeps/unix/sysv/linux/clock_nanosleep.c: No such file or directory.
Additionally, an error shows in the bottom right of VS Code, Failed to get Stack Trace: Selected thread is running. (from stack-info-depth --thread 1)
, and the process does not freeze after running launch.json
.
Issue Analytics
- State:
- Created a year ago
- Comments:14
Top Results From Across the Web
gdb cannot attach to process - linux - Stack Overflow
When trying to attach gdb to hanging process as root user, I got the following: Attaching to process 9636 Could not attach to...
Read more >Unable to Attach to the Process - Visual Studio (Windows)
Run the debugger and managed application under the same user account name and password. To solve Scenario 2. From the Start menu, choose...
Read more >after upgrade gdb won't attach to process - Ask Ubuntu
Attaching to process 10144 Could not attach to process. If your uid matches the uid of the target process, check the setting of ......
Read more >New debugger does not attach to process #623 - GitHub
Launch a js process; Debugger fails to attach. ... I'm emailing a log file to the email address with this issue's link as...
Read more >Could not attach to process: The request is not supported.
I am having a problem with a release build on a customer's x64 server 2008 box. My application is giving "<Application Name> has...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
you can execute that statement in the console before / after setting breakpoints - if that is what you want, too
That’s a bit strange. I’d try adding
"autorun": [ "set breakpoint pending on" ]
to launch configuration.