From: cworth@cworth.org (Carl Worth)
Subject: [sup-talk] Exception trying to run git source
Date: Wed, 19 Aug 2009 12:40:15 -0700 [thread overview]
Message-ID: <1250710221-sup-925@yoom.home.cworth.org> (raw)
In-Reply-To: <1250707794-sup-6173@masanjin.net>
Excerpts from William Morgan's message of Wed Aug 19 11:52:26 -0700 2009:
> > no Redwood::SentManager instance defined in method call to i_am_the_instance!
> > ./lib/sup/util.rb:512:in `method_missing'
> > /usr/lib/ruby/1.8/sup/sent.rb:10:in `initialize'
> > ./lib/sup/util.rb:524:in `new'
> > ./lib/sup/util.rb:524:in `init'
> > ./lib/sup.rb:110:in `start'
> > ./bin/sup:138
>
> Do you get this error in next head, and in the "first bad commit" you
> reported?
Yes.
> Neither of those should have any calls to i_am_the_instance!
> anywhere in the code.
Thanks. That confirms that I'm not running the code I think I am, and
the above stack trace makes that obvious, (see
/usr/lib/ruby/1.8/sup/sent.rb). So I was running some unholy mixture
of the installed Debian sup and the from-git sup and it worked no
better than one would expect.
My previously reported crashes didn't happen to fail in a way that
made /usr/lib show up in the stack trace, but both crashes are fixed
by just moving /usr/lib/ruby/1.8/sup out of the way.
So I'm glad to have things working now, but I'm still curious to know
why ruby goes digging into /usr/lib/ruby/1.8 to find sup/sent.rb when
there's a ./lib/sub/sent.rb present and I've passed a "-I ./lib"
option to ruby, (and plainly, ruby is interpreting other files from
./lib).
And I'd be glad if someone could recommend a ruby-esque way to debug a
situation like this. I mean, I could obviously have just run ruby
under strace and looked for the paths of various *.rb files getting
loaded, but surely there's some more ruby-specific way to list files
that are being used?
-Carl
PS. I'm intrigued by the following mention:
You?ve got the same sort of command-line debugger available.
[http://www.ruby-lang.org/en/documentation/ruby-from-other-languages/to-ruby-from-c-and-c-/]
so that's clearly something I'm going to have to learn to use.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20090819/b7de0a71/attachment.bin>
next prev parent reply other threads:[~2009-08-19 19:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-19 0:49 Carl Worth
2009-08-19 2:47 ` Ben Walton
2009-08-19 15:59 ` Ben Walton
2009-08-19 16:19 ` William Morgan
2009-08-19 16:33 ` Carl Worth
2009-08-19 16:34 ` Ben Walton
2009-08-19 17:53 ` Carl Worth
2009-08-19 18:08 ` Ben Walton
2009-08-19 18:52 ` William Morgan
2009-08-19 19:40 ` Carl Worth [this message]
2009-08-19 20:02 ` William Morgan
2009-08-19 21:37 ` Carl Worth
2009-08-22 20:23 ` William Morgan
2009-08-26 21:26 ` Carl Worth
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1250710221-sup-925@yoom.home.cworth.org \
--to=cworth@cworth.org \
/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