Running with --luanch-profile

[NeuSandeZ]

I'm having troubles invoking this command

you can now set dotnet run parameters in 2 ways:

pass them as netcoredbg arguments:
$>netcoredbg [netcoredbg params] [-- dotnet run [run params]] [-- [your_app_params]]

here's where I found it https://github.com/Samsung/netcoredbg/issues/68

What I've tried:

> netcoredbg --interpreter=cli -- dotnet bin/Debug/net9.0/ApiTest.dll
ncdb> r -- --launch-profile http 

(this doesn't respect the launch profile option, but hit breakpoints)

> netcoredbg --interpreter=cli -- dotnet run --launch-profile http
ncdb> b Program.cs:51
ncdb> r 

(this does respect the launch profile, however breakpoints are not hit, seems like upon "r" command new dotnet process is created and ncdb cannot attach to it, or having troubles with loading symbols)

I tried various variations of these commands and I just cannot get it to work.

By the way is this project still alive? It's been over a year since last commit and release and .net 10 is knocking at our doors.

[viewizard]

ncdb> r -- --launch-profile http

This one don't supported now, supported ways you could see here: #68 (comment)

you can now set dotnet run parameters in 2 ways:

1. pass them as netcoredbg arguments:
   $>netcoredbg [netcoredbg params] [-- dotnet run [run params]] [-- [your_app_params]]
2. set them by set args command:
   ncdb> file dotnet
   ncdb> set args run [run params] [-- [your_app_params]]

Accordingly https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet-run you probably should try something like netcoredbg --interpreter=cli -- dotnet run --launch-profile http bin/Debug/net9.0/ApiTest.dll.

Did you try start you program with profiling but without debugger?

[gbalykov]

It's been over a year since last commit and release and .net 10 is knocking at our doors.

We plan to make a new release later this year, which will include PRs that are already approved, as well as .net 10 support.

[NeuSandeZ]

It's been over a year since last commit and release and .net 10 is knocking at our doors.

We plan to make a new release later this year, which will include PRs that are already approved, as well as .net 10 support.

Glad to hear that

[NeuSandeZ]

Accordingly https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet-run you probably should try something like netcoredbg --interpreter=cli -- dotnet run --launch-profile http bin/Debug/net9.0/ApiTest.dll.

I tried above and it didn't work.

Did you try start you program with profiling but without debugger?

Yes I launched the app without debugger, and the profiling worked as expected. Also when I run the app from CLI, it picks up the correct profile and after that I just attach to that process so that's how I managed to debug it correctly. I just thought I could achieve launching app with correct settings and debugging it with one command/action.

[viewizard]

Also when I run the app from CLI, it picks up the correct profile and after that I just attach to that process so that's how I managed to debug it correctly.

Could you please provide process tree in case you run the app from CLI with --launch-profile?

I just thought I could achieve launching app with correct settings and debugging it with one command/action.

I am not sure how exactly --launch-profile work, but this looks like it create some additional managed application that after that lauch you program. netcoredbg create process and attach to first managed application only, so, in case profiler is some kind of managed application too that start first - you will "debug" profiler instead of your application. In this case attach netcoredbg to proper process is only option you have.

[NeuSandeZ]

>ps -o pid,ppid,command | grep 55220

55220 54718 dotnet run --launch-profile http 
55221 55220 /Users/username/Projects/ApiTest/bin/Debug/net10.0/ApiTest

That would be the tree.

In this case attach netcoredbg to proper process is only option you have.

But what about this?

https://github.com/Samsung/netcoredbg/issues/68

$>netcoredbg [netcoredbg params] [-- dotnet run [run params]] [-- [your_app_params]]

This indicates that I should be able to pass [run params] to netcoredbg directly and --launch-profile is one of them. Is it no longer valid?

[viewizard]

>ps -o pid,ppid,command | grep 55220

55220 54718 dotnet run --launch-profile http 
55221 55220 /Users/username/Projects/ApiTest/bin/Debug/net10.0/ApiTest

That would be the tree.

Looks like 2 managed processes, please provide ps axf output with part that start from netcoredbg.

$>netcoredbg [netcoredbg params] [-- dotnet run [run params]] [-- [your_app_params]]

This indicates that I should be able to pass [run params] to netcoredbg directly and --launch-profile is one of them. Is it no longer valid?

This is valid, but this looks like you have 2 managed processes:

55220 54718 dotnet run --launch-profile http
55221 55220 /Users/username/Projects/ApiTest/bin/Debug/net10.0/ApiTest

and as I mentioned above, netcoredbg will debug first one, 55220 in your case, not 55221 (your app).

[NeuSandeZ]

What I did:

Launch command:
> netcoredbg --interpreter=cli -- dotnet run --launch-profile http
ncdb> b Program.cs:41
ncdb> r

after that I search for processes:

> ps -axf | rg netcoredbg
  501 64592 61532   0 11:39AM ttys001    0:00.01 netcoredbg --interpreter=cli -- dotnet run --launch-profile http
  501 64866 62381   0 11:39AM ttys002    0:00.00 rg netcoredbg
> ps -axf | rg ApiTest
  501 64885 64884   0 11:40AM ttys001    0:00.16 /Users/username/Projects/ApiTest/bin/Debug/net10.0/ApiTest
  501 65012 62381   0 11:40AM ttys002    0:00.00 rg ApiTest

[viewizard]

Please provide output for ps axf. This should looks like

   1595 ?        Ss     0:04 /usr/lib/systemd/systemd --user
   1596 ?        S      0:00  \_ (sd-pam)
   1605 ?        Ssl   18:26  \_ /usr/bin/pipewire
   1606 ?        Ssl    0:00  \_ /usr/bin/pipewire -c filter-chain.conf

or something like this with tree view. Don't search, don't grep, etc, just post it as is here please.

[NeuSandeZ]

I don't have access to ps axf because unfortunately I'm on macOS. I just used a little script to print out a tree like that. Should be this:

      79693 79416 netcoredbg --interpreter=cli -- dotnet run --launch-profile http
        79695 79693 /Users/wojciechmassalski/.local/share/mise/installs/dotnet/10.0.100-rc.2.25502.107/dotnet run --launch-profile http
          79696 79695 /Users/wojciechmassalski/Projects/ApiTest/bin/Debug/net10.0/ApiTest

[viewizard]

This mean, that dotnet with --launch-profile option create separate profiler managed process, debugger start debug session for this managed process and after this profiler managed process create child (your app) managed process. netcoredbg don't support switch and debug child managed processes. Attach to process for debug the only option for this case.