Hi,
Pierre Neidhardt skribis:
> Ricardo Wurmus writes:
>
>> diff --git a/nix/libstore/build.cc b/nix/libstore/build.cc
>> index 29266f1dd6..94609e07f5 100644
>> --- a/nix/libstore/build.cc
>> +++ b/nix/libstore/build.cc
>> @@ -2247,6 +2247,7 @@ void DerivationGoal::runChild()
>>
Marius Bakke writes:
> Pierre Neidhardt writes:
>
>> Marius Bakke writes:
>>
>>> You can run it directly from a shell, and/or attach a debugger.
>>
>> Thanks for the tip.
>>
>> Any idea how to attach Geiser to it?
>
> The daemon is a C++ program, so I'm not sure that would work ...
>
> If
Marius Bakke writes:
> The daemon is a C++ program, so I'm not sure that would work ...
Hahaha, completely forgot :D
--
Pierre Neidhardt
https://ambrevar.xyz/
signature.asc
Description: PGP signature
Pierre Neidhardt writes:
> Marius Bakke writes:
>
>> You can run it directly from a shell, and/or attach a debugger.
>
> Thanks for the tip.
>
> Any idea how to attach Geiser to it?
The daemon is a C++ program, so I'm not sure that would work ...
If you are trying to increase the trace width
Hi,
Pierre Neidhardt skribis:
> The COLUMN environment option (set in root's .bash_profile) does not
> extend the print width of backtraces when running `guix build`.
I understand, but which backtraces are we talking about?
COLUMNS only helps if you wish to debug ‘guix build’ itself. It
Pierre Neidhardt writes:
> Ludovic Courtès writes:
>
>> Users are not supposed to see backtraces coming from the daemon or its
>> helpers (‘guix substitute’, ‘guix offload’, etc.).
>
> How are we supposed to debug Guix daemon errors?
You can run it directly from a shell, and/or attach a
Ludovic Courtès writes:
> Users are not supposed to see backtraces coming from the daemon or its
> helpers (‘guix substitute’, ‘guix offload’, etc.).
How are we supposed to debug Guix daemon errors?
--
Pierre Neidhardt
https://ambrevar.xyz/
signature.asc
Description: PGP signature
Tobias Geerinckx-Rice writes:
> Nor should it[0]. What you describe sounds like a convenient bug
> being fixed(?). Was this on Guix System or a foreign
> distribution?
Guix System.
--
Pierre Neidhardt
https://ambrevar.xyz/
signature.asc
Description: PGP signature
Hullo,
Ludovic Courtès 写道：
Users are not supposed to see backtraces coming from the daemon
or its
helpers (‘guix substitute’, ‘guix offload’, etc.).
Put that in the EULA then, because those naughty users insist on
doing so regularly :-) It's not clear what you're arguing for.
Pierre
Hi,
Pierre Neidhardt skribis:
> This has stopped working for me a while ago.
What stopped working exactly?
Users are not supposed to see backtraces coming from the daemon or its
helpers (‘guix substitute’, ‘guix offload’, etc.).
Thanks,
Ludo’.
Pierre Neidhardt writes:
> This has stopped working for me a while ago.
> Could it be that Guile's behaviour changed here?
Is this increase a function of Guix, or of Guile? This is a constant
source of pain for me as I package things since very useful information
is often elided due to this
This has stopped working for me a while ago.
Could it be that Guile's behaviour changed here?
--
Pierre Neidhardt
https://ambrevar.xyz/
signature.asc
Description: PGP signature
Hello Pierre,
Pierre Neidhardt writes:
> Ricardo Wurmus writes:
>
>> Set the COLUMNS environment variable to some large value.
>
> Hmm... I use Eshell (in Emacs), in which the COLUMNS env variable is
> automatically
> set to the Emacs window width. For instance right now I have 190. And
>
On 15. Jul 2019, at 20:38, Robert Vollmert wrote:
>
>> On 15. Jul 2019, at 17:40, Ricardo Wurmus wrote:
>>
>> P writes:
>>
Hi Pierre,
> Quite often when packaging and iterating, the daemon produces backtraces
> on errors, which could be very useful to understand what's
> On 15. Jul 2019, at 17:40, Ricardo Wurmus wrote:
>
>
> P writes:
>
>>> Hi Pierre,
>>>
Quite often when packaging and iterating, the daemon produces backtraces
on errors, which could be very useful to understand what's wrong, but
unfortunately the output is truncated to
P writes:
>> Hi Pierre,
>>
>> > Quite often when packaging and iterating, the daemon produces backtraces
>> > on errors, which could be very useful to understand what's wrong, but
>> > unfortunately the output is truncated to some 80-ish column.
>>
>> Set the COLUMNS environment variable to
> Hi Pierre,
>
> > Quite often when packaging and iterating, the daemon produces backtraces
> > on errors, which could be very useful to understand what's wrong, but
> > unfortunately the output is truncated to some 80-ish column.
>
> Set the COLUMNS environment variable to some large value.
>
>
On 2019-07-15 14:47, Ricardo Wurmus wrote:
Hi Pierre,
Quite often when packaging and iterating, the daemon produces backtraces
on errors, which could be very useful to understand what's wrong, but
unfortunately the output is truncated to some 80-ish column.
Set the COLUMNS environment
Ricardo Wurmus writes:
> Set the COLUMNS environment variable to some large value.
Hmm... I use Eshell (in Emacs), in which the COLUMNS env variable is
automatically
set to the Emacs window width. For instance right now I have 190. And
the daemon still displays truncated message (i.e. way
Hi Pierre,
> Quite often when packaging and iterating, the daemon produces backtraces
> on errors, which could be very useful to understand what's wrong, but
> unfortunately the output is truncated to some 80-ish column.
Set the COLUMNS environment variable to some large value.
--
Ricardo
20 matches
Mail list logo
