Weird problem with expenses object
-
Andreas Flack
Weird problem with expenses object
Tue October 07 2008 18:00:37 UTCHi!
I'm hacking on o.o.expenses a bit and have encountered a weird problem:
In the database, the person field is set correctly, and in edit forms,
the person information is displayed correctly. In list views, the person
column, which is normally filled by DM get_content_html remains empty.
Now for the strange part: When I try to put this line into a style element:
var_dump($view['person']);
Apache produces a Segfault looking like this:
** (process:28981): DEBUG: Midgard: select_database opened database
midgardlive
(process:28981): midgard-core-DEBUG: query=SELECT
id,style,root,lang,info&1,Length(prefix),sitegroup FROM host WHERE
name='myserver' AND port in (0,80) AND ( (0 <> 0 AND prefix = '') OR (0
= 0 AND
prefix=Left('/openpsa2/expenses/hours/task/a63220d0c85811dcb22d1330aeaa22002200/',Length(prefix))
AND
IF(67>=Length(prefix),MID('/openpsa2/expenses/hours/task/a63220d0c85811dcb22d1330aeaa22002200/',1+Length(prefix),1)
IN ('','/'),0)=1 ) ) AND online <> 0 AND host.metadata_deleted=0
ORDER BY prefix DESC, port DESC
(process:28981): midgard-core-DEBUG: query=SELECT info&1 FROM page WHERE
page.id=305
(process:28981): midgard-core-DEBUG: query=SELECT info&2 FROM page WHERE
page.id=305
(process:28981): midgard-core-DEBUG: query=SELECT style FROM page WHERE
page.id=305
(process:28981): midgard-core-DEBUG: query=SELECT
id,style,info&1,info&2,author,owner FROM page WHERE up=305 AND
name='expenses' AND page.metadata_deleted=0
(process:28981): midgard-core-DEBUG: query=SELECT page FROM cache WHERE
host=61 and page=305 AND style=68 AND lang=0 LIMIT 1
(process:28981): midgard-core-DEBUG: query=SELECT title,content FROM
page_i WHERE sid=305 AND lang=0
(process:28981): midgard-core-DEBUG: query=SELECT pageelement.id AS
id,name,value FROM pageelement, pageelement_i WHERE page=305 AND
pageelement.id=pageelement_i.sid AND pageelement_i.lang=0 AND
pageelement.sitegroup IN (0, 1) AND pageelement.metadata_deleted=0
(process:28981): midgard-core-DEBUG: query=SELECT up FROM page WHERE
page.id=305
(process:28981): midgard-core-DEBUG: query=SELECT element.id AS
id,name,value FROM element, element_i WHERE style=68 AND
element.id=element_i.sid AND element_i.lang=0 AND element.sitegroup IN
(0, 1) AND element.metadata_deleted=0
(process:28981): midgard-core-DEBUG: query=SELECT up FROM style WHERE
style.id=68
(process:28981): midgard-core-DEBUG: query=SELECT element.id AS
id,name,value FROM element, element_i WHERE style=67 AND
element.id=element_i.sid AND element_i.lang=0 AND element.sitegroup IN
(0, 1) AND element.metadata_deleted=0
(process:28981): midgard-core-DEBUG: query=SELECT up FROM style WHERE
style.id=67
** (process:28981): DEBUG: Midgard: select_database kept current
database midgardlive
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1216457024 (LWP 28981)]
0xb7ba0463 in strlen () from /lib/tls/i686/cmov/libc.so.6
(gdb) backtrace
#0 0xb7ba0463 in strlen () from /lib/tls/i686/cmov/libc.so.6
#1 0xb6e3f4d7 in _estrdup () from /usr/lib/apache2/modules/libphp5.so
#2 0xb6936e81 in xdebug_xmlize (string=0x0, len=0, newlen=0xbfbfacd4)
at /tmp/pear/temp/xdebug/xdebug_var.c:1139
#3 0xb693624e in xdebug_var_export_fancy (struc=0xbfbfad24,
str=0xbfbfad04,
level=1, debug_zval=0, options=0x8811488)
at /tmp/pear/temp/xdebug/xdebug_var.c:934
#4 0xb693688e in xdebug_get_zval_value_fancy (name=0x0, val=0xad28f4ac,
len=0xbfbfad40, debug_zval=0, options=0x8811488)
at /tmp/pear/temp/xdebug/xdebug_var.c:1025
#5 0xb691e046 in zif_xdebug_var_dump (ht=1, return_value=0xad2a3db8,
return_value_ptr=0x0, this_ptr=0x0, return_value_used=0)
at /tmp/pear/temp/xdebug/xdebug.c:2612
#6 0xb6e75530 in execute_internal () from
/usr/lib/apache2/modules/libphp5.so
#7 0xb691b41f in xdebug_execute_internal (current_execute_data=0xbfbfb12c,
return_value_used=0) at /tmp/pear/temp/xdebug/xdebug.c:1605
#8 0xb6e871cb in execute () from /usr/lib/apache2/modules/libphp5.so
#9 0xb6e76de8 in execute () from /usr/lib/apache2/modules/libphp5.so
#10 0xb691b0c3 in xdebug_execute (op_array=0xad29f178)
at /tmp/pear/temp/xdebug/xdebug.c:1541
#11 0xb6e7d01b in execute () from /usr/lib/apache2/modules/libphp5.so
#12 0xb6e76de8 in execute () from /usr/lib/apache2/modules/libphp5.so
#13 0xb691b0c3 in xdebug_execute (op_array=0xad449f24)
---Type <return> to continue, or q <return> to quit---
at /tmp/pear/temp/xdebug/xdebug.c:1541
#14 0xb6e86dd1 in execute () from /usr/lib/apache2/modules/libphp5.so
#15 0xb6e76de8 in execute () from /usr/lib/apache2/modules/libphp5.so
#16 0xb691b0c3 in xdebug_execute (op_array=0x883e440)
at /tmp/pear/temp/xdebug/xdebug.c:1541
#17 0xb6e86dd1 in execute () from /usr/lib/apache2/modules/libphp5.so
#18 0xb6e76de8 in execute () from /usr/lib/apache2/modules/libphp5.so
#19 0xb691b0c3 in xdebug_execute (op_array=0xad86deec)
at /tmp/pear/temp/xdebug/xdebug.c:1541
#20 0xb6e86dd1 in execute () from /usr/lib/apache2/modules/libphp5.so
#21 0xb6e76de8 in execute () from /usr/lib/apache2/modules/libphp5.so
#22 0xb691b0c3 in xdebug_execute (op_array=0xad8d958c)
at /tmp/pear/temp/xdebug/xdebug.c:1541
#23 0xb6e86dd1 in execute () from /usr/lib/apache2/modules/libphp5.so
#24 0xb6e76de8 in execute () from /usr/lib/apache2/modules/libphp5.so
#25 0xb691b0c3 in xdebug_execute (op_array=0xad8cd8e4)
at /tmp/pear/temp/xdebug/xdebug.c:1541
#26 0xb6e86dd1 in execute () from /usr/lib/apache2/modules/libphp5.so
#27 0xb6e76de8 in execute () from /usr/lib/apache2/modules/libphp5.so
#28 0xb691b0c3 in xdebug_execute (op_array=0xae4215b8)
at /tmp/pear/temp/xdebug/xdebug.c:1541
#29 0xb6e86dd1 in execute () from /usr/lib/apache2/modules/libphp5.so
#30 0xb6e76de8 in execute () from /usr/lib/apache2/modules/libphp5.so
---Type <return> to continue, or q <return> to quit---
#31 0xb691b0c3 in xdebug_execute (op_array=0xae46fa24)
at /tmp/pear/temp/xdebug/xdebug.c:1541
#32 0xb6e86dd1 in execute () from /usr/lib/apache2/modules/libphp5.so
#33 0xb6e76de8 in execute () from /usr/lib/apache2/modules/libphp5.so
#34 0xb691b0c3 in xdebug_execute (op_array=0xae61b50c)
at /tmp/pear/temp/xdebug/xdebug.c:1541
#35 0xb6e57fbc in zend_execute_scripts ()
from /usr/lib/apache2/modules/libphp5.so
#36 0xb6e13272 in php_execute_script ()
from /usr/lib/apache2/modules/libphp5.so
#37 0xb6edb913 in php_ap2_register_hook ()
from /usr/lib/apache2/modules/libphp5.so
#38 0x08074607 in ap_run_handler ()
#39 0x080777b1 in ap_invoke_handler ()
#40 0x08084898 in ap_process_request ()
#41 0x08081b0e in ap_register_input_filter ()
#42 0x0807b447 in ap_run_process_connection ()
#43 0x080888a4 in ap_graceful_stop_signalled ()
#44 0x08088b04 in ap_graceful_stop_signalled ()
#45 0x080898ac in ap_mpm_run ()
#46 0x0806224f in main ()
I don't really know how to proceed. The apache logfiles show warnings like:
(process:29069): GLib-WARNING **: gmessages.c:387: could not find
handler with id `2' for domain "midgard-core"
(process:29068): GLib-WARNING **: gmessages.c:387: could not find
handler with id `7' for domain "midgard-core"
(process:29076): GLib-WARNING **: gmessages.c:387: could not find
handler with id `7' for domain "midgard-core"
(process:29069): GLib-WARNING **: gmessages.c:387: could not find
handler with id `3' for domain "midgard-core"
(process:29068): GLib-WARNING **: gmessages.c:387: could not find
handler with id `8' for domain "midgard-core"
But I don't think they came from the same request. Apart from that,
everything looks like it should. If someone has an idea where I could
look, pls let me know.
Bye,
Andreas
P.S.: congratulations on shipping :-)
_______________________________________________
dev mailing list
dev@lists.midgard-project.org
http://lists.midgard-project.org/mailman/listinfo/dev -
-
Re: [midgard-dev] Weird problem with expenses object
Tue October 07 2008 21:21:32 UTCAndreas Flack writes:
> Hi!
Hi!
> #0 0xb7ba0463 in strlen () from /lib/tls/i686/cmov/libc.so.6
> #1 0xb6e3f4d7 in _estrdup () from /usr/lib/apache2/modules/libphp5.so
> #2 0xb6936e81 in xdebug_xmlize (string=0x0, len=0, newlen=0xbfbfacd4)
> at /tmp/pear/temp/xdebug/xdebug_var.c:1139
> #3 0xb693624e in xdebug_var_export_fancy (struc=0xbfbfad24,
> str=0xbfbfad04,
Looks like it segfaults in xdebug. Disable it for a while and var_dump
again.
Also it's good idea to send backtrace to xdebug developer.
They kindly accept any reports.
> I don't really know how to proceed. The apache logfiles show warnings like:
>
> (process:29069): GLib-WARNING **: gmessages.c:387: could not find
> handler with id `2' for domain "midgard-core"
To be honest... I have no idea how to reproduce it.
But it's only warning and should be harmless.
Piotras
_______________________________________________
dev mailing list
dev@lists.midgard-project.org
http://lists.midgard-project.org/mailman/listinfo/dev -
