snapd debug without systemd activation

John Lenton john.lenton at canonical.com
Mon Dec 5 09:32:40 UTC 2016


ah! then maybe the easiest way is indeed to create the sockets yourself.
We had meant to add that support at some point but the need was never
present. If your patch works for you for now, feel free to continue
using it; I'll look into this at some point this week.

On 5 December 2016 at 09:30, Boris Rybalkin <ribalkin at gmail.com> wrote:
> John,
>
> I am new to go language (coming from Java world) I want to debug with
> breakpoints from IDE (and I was able aftet adding socket creation code).
>
> Maybe I should run it with systemd and then attach to it from IDE?
>
> On 5 Dec 2016 09:23, "John Lenton" <john.lenton at canonical.com> wrote:
>
> On 5 December 2016 at 08:58, Boris Rybalkin <ribalkin at gmail.com> wrote:
>>
>> Is it possible to run snapd for debugging without systemd socket
>> activation?
>
> depends on what you mean. At the end of HACKING.md in the root of the
> project there are instructions for how to run snapd by hand, using
> systemd-activate:
>
> https://github.com/snapcore/snapd/blob/master/HACKING.md#testing-snapd
>
> Is that what you're looking for?
>
> --
> Snapcraft mailing list
> Snapcraft at lists.snapcraft.io
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/snapcraft
>
>
>
> --
> Snapcraft mailing list
> Snapcraft at lists.snapcraft.io
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/snapcraft
>




More information about the Snapcraft mailing list