unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: 45mg <45mg.writes@gmail.com>
To: "Attila Lendvai" <attila@lendvai.name>, "Ludovic Courtès" <ludo@gnu.org>
Cc: Maxim Cournoyer <maxim.cournoyer@gmail.com>,
	zimoun <zimon.toutoune@gmail.com>,
	guix-devel <guix-devel@gnu.org>
Subject: Globally configure Guile compiler optimization? (was: Re: Guile debugger workgroup?)
Date: Mon, 06 Jan 2025 09:26:22 -0500	[thread overview]
Message-ID: <87sepwrpbl.fsf@gmail.com> (raw)
In-Reply-To: <2m-RU6GKIEuW6fwb1WzaIhGyxUcl0eRO1o3xiVUTqIoVzrmdplzfGTAGBxrToB_Ii55lnXjVEyOtRPzI_iSuwuTQ733CjZ8XAvv39Ho6EGQ=@lendvai.name>

Hi Guix,

Attila Lendvai <attila@lendvai.name> writes:

> i'm sure there's a way to globally override the
> debug/optimization/inlining level in guile to make sure the code
> compiles in a way that no breakpoints are missed (and/or backtraces
> remain more intact, etc).
>
> this should also be added to the documentation, especially in the guix
> context, where it's very much not as trivial as to change a command
> line argument to e.g. start the guix daemon, or shepherd, in a
> configuration that makes things more debuggable.

It has been over 2 years since this message was posted, and I am still
unable to find a way to do this. Has anyone figured it out yet?

I'm not even sure if it /would/ improve anything, but it seems like
something worth trying.

For me at least, near-useless Guile backtraces are by far the biggest
hindrance in writing code for Guix.


  parent reply	other threads:[~2025-01-06 14:27 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20221027035100.28852-1-maxim.cournoyer@gmail.com>
     [not found] ` <20221027035100.28852-3-maxim.cournoyer@gmail.com>
     [not found]   ` <87leojon1z.fsf_-_@gnu.org>
     [not found]     ` <877d03xywl.fsf@gmail.com>
     [not found]       ` <87sfihfpng.fsf_-_@gnu.org>
     [not found]         ` <86zgcpju9p.fsf@gmail.com>
     [not found]           ` <87y1s82o23.fsf@gmail.com>
     [not found]             ` <87zgckwdtw.fsf@gmail.com>
     [not found]               ` <87sficqb71.fsf@gmail.com>
     [not found]                 ` <86fsebdpl9.fsf@gmail.com>
2022-11-25 15:23                   ` Guile debugger workgroup? (was: Coding style: similarly-named variables) Maxim Cournoyer
2022-11-26 11:22                     ` Guile debugger workgroup? Ludovic Courtès
2022-11-27  3:16                       ` Maxim Cournoyer
2022-11-28 10:53                         ` Ludovic Courtès
2022-11-28 13:41                           ` Attila Lendvai
2022-11-28 14:50                             ` Maxim Cournoyer
2022-11-29  8:46                             ` Ludovic Courtès
2022-11-30  3:44                               ` Attila Lendvai
2025-01-06 14:26                             ` 45mg [this message]
2022-11-27 12:04                       ` zimoun
2022-11-28  0:27                         ` Maxim Cournoyer
2022-11-28 11:06                         ` Ludovic Courtès
2022-11-28 12:31                           ` zimoun
2022-11-27 20:46                       ` Attila Lendvai
2022-11-28  0:41                         ` David Pirotte
2022-11-28  0:45                           ` David Pirotte
2022-11-28  2:06                         ` Maxim Cournoyer
2022-11-28  7:22                           ` Joshua Branson
2024-07-02 12:33                             ` Maxim Cournoyer
2022-11-28 11:09                         ` Ludovic Courtès
2022-11-28 14:12                           ` Attila Lendvai
2022-11-29  8:54                             ` Ludovic Courtès
2022-11-28 12:24                     ` Guile debugger workgroup? (was: Coding style: similarly-named variables) Csepp
2022-11-30  7:09                     ` Guile debugger workgroup? Jannneke Nieuwenhuizen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sepwrpbl.fsf@gmail.com \
    --to=45mg.writes@gmail.com \
    --cc=attila@lendvai.name \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    --cc=zimon.toutoune@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).