unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Matt Wette <mwette@alumni.caltech.edu>
Cc: 19540@debbugs.gnu.org
Subject: bug#19540: repeated ./././ in compiled modules
Date: Mon, 19 Jan 2015 21:28:05 +0100	[thread overview]
Message-ID: <877fwiy0q2.fsf@gnu.org> (raw)
In-Reply-To: <188846A3-246A-49DB-95F0-37FEE6903C85@alumni.caltech.edu> (Matt Wette's message of "Sat, 10 Jan 2015 14:45:00 -0800")

Matt Wette <mwette@alumni.caltech.edu> skribis:

> 1) I found that this problem persists across restarts of guile.  I have been debugging a module in current dir and I am seeing the path extend an extra "./" every time I type ",reload (lalr1).
>
> 2) My environment includes
>    GUILE_LOAD_PATH=.:/Users/mwette/opt/guile

The problem stems from the ‘.’ entry in the search path.  On one hand
this is perfectly valid; on the other hand, it’s usually frowned upon,
because you may end up executing possibly malicious code that just
happens to be in $PWD.

All in all, I recommend using only absolute directory names in the
search paths, which will also solve the initial problem.

Can you confirm?

Thanks,
Ludo’.





  reply	other threads:[~2015-01-19 20:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-09  4:13 bug#19540: minor: module path picking up ./././ Matt Wette
2015-01-10 22:45 ` bug#19540: repeated ./././ in compiled modules Matt Wette
2015-01-19 20:28   ` Ludovic Courtès [this message]
2015-01-19 22:19     ` Matt Wette
2015-01-20 21:12       ` Ludovic Courtès
2016-06-23  8:36         ` Andy Wingo
2016-06-23 13:06           ` Ludovic Courtès
2016-06-23 16:03             ` Andy Wingo
2016-06-24  8:28               ` Ludovic Courtès
2016-06-24  8:49                 ` Andy Wingo
2016-06-24  9:41                   ` Ludovic Courtès
2015-01-18 16:09 ` bug#19540: also generates problem for debugger tracebacks Matt Wette

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://www.gnu.org/software/guile/

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

  git send-email \
    --in-reply-to=877fwiy0q2.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=19540@debbugs.gnu.org \
    --cc=mwette@alumni.caltech.edu \
    /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. 
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).