Ooooh there's an easier way. Type this in your console:
>> localStorage.debugging = "spawn"
And then refresh (F5). But in any case this should be documented and
made less sucky.
Stef
On Tue, Apr 21, 2020 at 1:35 PM Stef Walter <[email protected]> wrote:
>
> The way I usually do it is open a javascript console and type:
>
> >> window.debugging = "all"
>
> And then cockpit should start spewing output into the console.
>
> If you want to just do "spawn" it's a little more tricky, as you (now)
> have to get that command into the right cockpit frame:
>
> >> for (x in window.frames) { x.debugging = "spawn"; };
>
> Hope that helps. This sounds like something we should document, and
> perhaps make the second case a bit better.
>
> Cheers,
>
> Stef
>
>
> On Wed, Apr 8, 2020 at 11:10 PM Justin Stephenson <[email protected]> wrote:
> >
> > Hi,
> >
> > I am looking to debug an issue in my cockpit
> > module(cockpit-session-recording) as I believe I am not getting all the
> > output from the cockpit spawn returned object. I have a few questions from
> > my initial investigation:
> >
> > In src/base1/cockpit.js I see:
> >
> > function spawn_debug() {
> > if (window.debugging == "all" || window.debugging == "spawn")
> > console.debug.apply(console, arguments);
> > }
> >
> > How do I enable this debugging?
> >
> > I also went through the below steps but I'm not sure which cockpit process
> > I need to debug.
> >
> > https://github.com/cockpit-project/cockpit/blob/master/HACKING.md#running-cockpit-processes-under-a-debugger
> >
> > Is it correct to assume cockpit_pipe_spawn() in src/common/cockpitpipe.c is
> > the C interface that the cockpit.spawn API calls underneath?
> >
> > If there are better ideas, or i'm going about this in the wrong way then
> > I'm open to suggestions.
> >
> > Thank you in advance.
> >
> > -Justin
> > _______________________________________________
> > cockpit-devel mailing list -- [email protected]
> > To unsubscribe send an email to [email protected]
> > Fedora Code of Conduct:
> > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives:
> > https://lists.fedorahosted.org/archives/list/[email protected]
>
>
>
> --
> Stef Walter (he / his)
> Linux Engineering
> Red Hat
--
Stef Walter (he / his)
Linux Engineering
Red Hat
_______________________________________________
cockpit-devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedorahosted.org/archives/list/[email protected]
