# Segfaults with 2.0.2 and named routes

**URL:** <https://www.ruby-forum.com/t/segfaults-with-2-0-2-and-named-routes/126039>\
**Category:** Rails\
**Created:** [January 14, 2008, 11:04pm UTC](https://www.ruby-forum.com/t/segfaults-with-2-0-2-and-named-routes/126039 "2008-01-14T23:04:02Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![snacktime](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/7feea3/32.png) [@snacktime](https://www.ruby-forum.com/u/snacktime)\
**Post date:** [January 14, 2008, 11:04pm UTC](https://www.ruby-forum.com/t/segfaults-with-2-0-2-and-named-routes/126039/1 "2008-01-14T23:04:02Z")

</div>

This is a really strange one. Latest ruby stable, rails 2.0.2, debian  
sid. About a dozen plugins installed which makes it more difficult to  
track down…

In routes.rb I have the following:

map.resources :profiles, :controller =\> :user\_profiles

So I’m using profile\_path(user\_obj) in my views. And I’m using  
acts\_as\_commentable.

profile\_path(current\_user), where current\_user is from  
acts\_as\_authenticated works fine. But when I get a user object from  
Model.comments.users, and pass that to profile\_path, immediate  
segfault. Using ruby-debug to step through a line running mongrel  
only confirms this is where it’s bombing, I haven’t been able to track  
it down further yet. Even more interesting is that it only segfaults  
the second time the code is run (second page load in the same  
process).

Ya so I know what to do next, but though I’d post this in case someone  
might have an idea where to look first.

Chris