Debug button fails when source member is not in same library as object

[dariocs]

Debug fails when source member is not in same library as object .

Reproduction steps:

Open a source member located in a different library than the compiled object (example member path: /MYLIB/QRPGLESRC/TEST.SQLRPGLE).
Press the extension's Debug button to start debugging .

Observe the error.
Failed to determine object type. Ensure the object exists and is a program (*PGM) or service program (*SRVPGM).

Actual behavior:
Debug fails with the error: "Failed to determine object type. Ensure the object exists and is a program (*PGM) or service program (*SRVPGM)."

Expected behavior:
Debug should start for the object regardless of the source member being in a different library, or provide clear guidance on required library/source layout.

---

Context	Version
Code for IBM i version	2.17.2
Visual Studio Code version	1.105.1
Operating System	win32_x64

Active extensions

Account Microsoft (microsoft-authentication): 0.0.1
Autenticazione GitHub (github-authentication): 0.0.2
Azione per server pronto (debug-server-ready): 1.0.0
Browse Lite (browse-lite): 0.3.9
COBOL (cobol): 25.10.18
Code for IBM i Walkthroughs (vscode-ibmi-walkthroughs): 0.5.0
Collegamento automatico per debug di Node (debug-auto-launch): 1.0.0
Creazione estensione (extension-editing): 1.0.0
Db2 for IBM i (vscode-db2i): 1.15.1
ESLint (vscode-eslint): 3.0.16
Emmet (emmet): 1.0.0
Error Lens (errorlens): 3.26.0
Esegui merge del conflitto (merge-conflict): 1.0.0
Excel Viewer (gc-excelviewer): 4.2.64
Funzionalità dei linguaggi TypeScript e JavaScript (typescript-language-features): 1.0.0
Funzionalità del linguaggio JSON (json-language-features): 1.0.0
GIT (git): 1.0.0
Git Base (git-base): 1.0.0
GitHub (github): 0.0.1
GitHub Copilot (copilot): 1.387.0
GitHub Copilot Chat (copilot-chat): 0.32.3
IBM i Debug (ibmidebug): 3.0.0
IBM i Notebooks (vscode-ibmi-notebooks): 0.0.6
IBM i Project Explorer (vscode-ibmi-projectexplorer): 2.12.3
IBM i Testing (vscode-ibmi-testing): 1.2.3
Java (oracle-java): 24.1.2
Live Server (LiveServer): 5.7.9
Modifica della configurazione (configuration-editing): 1.0.0
Path Intellisense (path-intellisense): 2.10.0
RPGLE (vscode-rpgle): 0.33.2
Source Orbit (vscode-sourceorbit): 1.4.1
Suggerimento terminale per VS Code (terminal-suggest): 1.0.1
Supporto di npm per VS Code (npm): 1.0.1
TODO Highlight (vscode-todo-highlight): 1.0.5

---

Remote system

Setting	Value
IBM i OS	V7R5M0
Tech Refresh	5
CCSID Origin	65535
Runtime CCSID	1144
Default CCSID	1144
SSHD CCSID	?
cqsh	true
SQL	Enabled
Source dates	Enabled

Enabled features

/QOpenSys/pkgs/bin	/usr/bin	/QSYS.lib/ILEDITOR.lib	/QSYS.LIB	/QIBM/ProdData/IBMiDebugService/bin	/QOpenSys/QIBM/ProdData/JavaVM/jdk80	/QOpenSys/QIBM/ProdData/JavaVM/jdk11	/QOpenSys/QIBM/ProdData/JavaVM/jdk17
bash	attr	GETNEWLIBL.PGM	QZDFMDB2.PGM	startDebugService.sh	64bit	64bit	64bit
chsh	iconv
find	setccsid
git	uname
grep
ls
md5sum
sort
stat
tar
tn5250

Shell env

BUILDLIB=XXX
CURLIB=XXX
EDITOR=vim
HOME=/home/xx
HOST=xx
LIBLS=QGPL QTEMP
LOGIN=xx
LOGNAME=xx
MAIL=/var/spool/mail/xx
OLDPWD=/home/xx
PASE_USRGRP_LIMITED=N
PATH=/QOpenSys/pkgs/bin:/QOpenSys/usr/bin:/usr/ccs/bin:/QOpenSys/usr/bin/X11:/usr/sbin:.:/usr/bin
PWD=/home/BFMI1778
SHELL=/QOpenSys/pkgs/bin/bash
SHLVL=1
TZ=<CET>-1<CEST>,M3.5.0,M10.5.0
USER=xxx
USERNAME=xxx
WORKDIR=/home/xxx
_=/QOpenSys/pkgs/bin/env

Variants

{
  "american": "#@$",
  "local": "��$",
  "qsysNameRegex": {}
}

[heymchri]

@dariocs how could the source know where the program is located that was compiled from that source? You should select the program object itself (the *PGM or *SRVPGM) in your object browser and debug that, or simply set an SEP on it.
I think the error message you're getting is correct - I don't think it was ever intended to be able to start a program debug from its source member. You debug from the program, and the source that was used to compile the program will pop up in your debug window so you can step through it.

[dariocs]

@heymchri It would be more correct to look it up in the library list (LIBL), the same way IBM i does when resolving program objects.Given that there is a button offering this option, reporting it as an error is misleading.