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

processesId picker only show part of process on the remote machine #10379

Closed
CatsOfMrXue opened this issue Jan 12, 2023 · 4 comments
Closed

processesId picker only show part of process on the remote machine #10379

CatsOfMrXue opened this issue Jan 12, 2023 · 4 comments
Labels
debugger fixed Check the Milestone for the release in which the fix is or will be available.
Milestone

Comments

@CatsOfMrXue
Copy link

Environment

  • OS and version:
    Windows 10 profession 21H1
  • VS Code:
    Version: 1.74.2 (user setup)
    Commit: e8a3071ea4344d9d48ef8a4df2c097372b0c5161
    Date: 2022-12-20T10:29:14.590Z
    Electron: 19.1.8
    Chromium: 102.0.5005.167
    Node.js: 16.14.2
    V8: 10.2.154.15-electron.0
    OS: Windows_NT x64 10.0.19043
    Sandboxed: No
  • C/C++ extension:
    Version 1.13.9
  • OS and version of remote machine (if applicable):
    Linux version 3.10.0-1160.71.1.el7.x86_64 ([email protected]) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-44) (GCC) ) Code completion with C/C++ extension #1 SMP Tue Jun 28 15:37:28 UTC 2022
  • GDB / LLDB version:
    GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-120.el7

Bug Summary and Steps to Reproduce

Bug Summary:

I want to attch to the remote target with ExtendedRemote mode,so I configrate my launch.json like
{ "name": "Attach with GDB", "type": "cppdbg", "request": "attach", "program": "<path to program>", "MIMode": "gdb", "miDebuggerPath": "/usr/bin/gdb", "miDebuggerServerAddress": "172.20.0.97:2159", "useExtendedRemote": true }
on the remote machine, i use the command gdbserver --multi :2159
then,the ProcessId Picker show the processes on my remote machine,but it only show part of the process on remote machine,because i can't find the process that i want to debug.but if i add "processId":"79068" to the launch.json,it works fine.
the 79068 is the target process ID which i get from ps -aux.BTW,i can use info os processes to find the target process ID on remote machine.

Steps to reproduce:

  1. type command gdbserver --multi :2159 on remote machine
  2. config the launch.json above
  3. start debug with the configration named "Attach with GDB"
  4. ProcessId Picker show only part of processes on the remote machine

Debugger Configurations

{
            "name": "Attach with GDB",
            "type": "cppdbg",
            "request": "attach",
            "program": "<path to program>",
            "MIMode": "gdb",
            "miDebuggerPath": "/usr/bin/gdb",
            "miDebuggerServerAddress": "172.20.0.97:2159",
            "useExtendedRemote": true
 }

Debugger Logs

there seem no infomation generated from the Debug Console or Output windows before i choose the exact process ID

Other Extensions

No response

Additional Information

No response

@WardenGnaw
Copy link
Member

@xisui-MSFT Can you help out on this issue of remote process picker not showing all of the process on the remote machine?

@WardenGnaw WardenGnaw added debugger investigate: repro This issue's repro steps needs to be investigated/confirmed labels Jan 12, 2023
@xisui-MSFT
Copy link
Contributor

@CatsOfMrXue Can you share the output of info os processes?

@CatsOfMrXue
Copy link
Author

@CatsOfMrXue Can you share the output of info os processes?
屏幕截图 2023-01-18 111359
the processes that i get from part of info os processes output is i want to attach,they are daemon

@sean-mcmanus sean-mcmanus added this to the 1.14.1 milestone Jan 18, 2023
@bobbrow bobbrow added the fixed Check the Milestone for the release in which the fix is or will be available. label Jan 24, 2023
@sean-mcmanus
Copy link
Contributor

A fix is available with 1.14.1 (pre-release): https://github.com/microsoft/vscode-cpptools/releases/tag/v1.14.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
debugger fixed Check the Milestone for the release in which the fix is or will be available.
Projects
None yet
Development

No branches or pull requests

5 participants