Closed (fixed)
Project:
Real Name
Version:
6.x-1.1-rc3
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
12 Nov 2008 at 20:14 UTC
Updated:
30 Nov 2008 at 14:23 UTC
One of my content types uses a field that is of type User Reference. After checking the "Reverse link" option in this field's config options, I get a white screen of death (and a report of a segmentation fault in my error_log) when I try to view a user profile. This only happens when RealName is enabled; that is, when I disable RealName, viewing user profiles works without a glitch.
I'm running 6.x-1.1-rc3, CCK 6.x-2.1 and PHP 5.1.6.
Can anyone else confirm this? I'm labeling it 'critical' since it causes a segmentation fault and accompanying WSoD.
Comments
Comment #1
nancydruI don't even know what a segmentation fault means. I don't know if I can set my test site up to test this.
Comment #2
nancydruI'm using CCK 6.x-2.0 and PHP 5.2.0 on Drupal 6.4 and I didn't get a problem.
Comment #3
nancydruI upgraded to CCK 6.x-2.1 and still no problems.
http://daemon80.blogspot.com/2007/10/solved-php-segmentation-fault.html
http://drupal.org/search/node/segmentation+fault
Comment #4
markj commentedI've set up the same versions of RealName and CCK on my laptop, which uses PHP 5.2.6, and can't replicate the problem even though the two Drupals are configured as identical as I can make them. I'll try it on another installation of Drupal on the same server and report back.
Comment #5
markj commentedI'm not sure what's causing the seg fault on my installation (which is RedHat Enterprise Linux), but AFAIK it's a generic problem that can have many causes. If we can't reproduce it using the same versions of contrib modules, then I suspect it is platform-specific, maybe even PHP-specific on a specific platform. Let me try replicating it on another Drupal instance on the same server. However, the fact that when I turn off RealName the problem goes away suggests that it's specific to that module or CCK running in conjunction with that module.
Comment #6
nancydruOr that the PHP code hits a known (and fixed) bug.
Comment #7
nancydruNo further follow up.