Re: [midgard-user] Segfault in DM2 edit forms
-
Marcin Sołtysiak
Re: [midgard-user] Segfault in DM2 edit forms
Thu July 17 2008 22:02:11 UTC>>> On my Kubuntu 8.04 installation, I noticed segfaults in some DM2 forms.
>>> Strangely enough, they only occur for some of my self-written MgdSchema
>>> objects (others and built-in ones are working fine), but I can't quite
>>> make out what the error could be. On a different machine (with openSUSE
>>> 9.2), they work fine, so I'm a bit lost.
>>>
>>> The backtrace looks like this:
>>>
>>> Program received signal SIGSEGV, Segmentation fault.
>>> [Switching to Thread 0xb77f2700 (LWP 8418)]
>>> 0xb6c79a13 in set_gobject_property_from_zobject (obj_ptr=0x9b65d2c,
>>> gobject=0x9a62540)
>>> at
>>> /home/sonic/downloads/software/Midgard_AllinOne-1.8.8/midgard-php4-1.8.8/midgard.c:627
>>>
>>> 627 if (propname && (*property)->refcount) {
>>
>> Did you test direct update/create/get on this objects?
>
> I tried update() with the DBA object and it produces the same backtrace.
> update() on the Midgard object is working, however.
How about nulls?
http://marcin.soltysiak.com/view/null-values-issue.html
Solt
_______________________________________________
user mailing list
user@lists.midgard-project.org
http://lists.midgard-project.org/mailman/listinfo/user -
Re: [midgard-user] Segfault in DM2 edit forms
Fri July 18 2008 10:54:34 UTCHi!
I tried setting all int and float fields to NOT NULL default 0, but that
doesn't mak a difference. Also, I have another MgdSchema type where
floats are nullable which is working fine, so my problem doesn't seem to
be related to that.
Bye,
Andreas
Marcin Sołtysiak schrieb:
>>>> On my Kubuntu 8.04 installation, I noticed segfaults in some DM2 forms.
>>>> Strangely enough, they only occur for some of my self-written MgdSchema
>>>> objects (others and built-in ones are working fine), but I can't quite
>>>> make out what the error could be. On a different machine (with openSUSE
>>>> 9.2), they work fine, so I'm a bit lost.
>>>>
>>>> The backtrace looks like this:
>>>>
>>>> Program received signal SIGSEGV, Segmentation fault.
>>>> [Switching to Thread 0xb77f2700 (LWP 8418)]
>>>> 0xb6c79a13 in set_gobject_property_from_zobject (obj_ptr=0x9b65d2c,
>>>> gobject=0x9a62540)
>>>> at
>>>> /home/sonic/downloads/software/Midgard_AllinOne-1.8.8/midgard-php4-1.8.8/midgard.c:627
>>>>
>>>>
>>>> 627 if (propname && (*property)->refcount) {
>>>
>>> Did you test direct update/create/get on this objects?
>>
>> I tried update() with the DBA object and it produces the same
>> backtrace. update() on the Midgard object is working, however.
>
> How about nulls?
>
> http://marcin.soltysiak.com/view/null-values-issue.html
>
> Solt
> _______________________________________________
> user mailing list
> user@lists.midgard-project.org
> http://lists.midgard-project.org/mailman/listinfo/user
_______________________________________________
user mailing list
user@lists.midgard-project.org
http://lists.midgard-project.org/mailman/listinfo/user -
Re: [midgard-user] Segfault in DM2 edit forms
Fri July 18 2008 11:17:41 UTCAndreas Flack writes:
> Hi!
>
> I tried setting all int and float fields to NOT NULL default 0, but that
> doesn't mak a difference. Also, I have another MgdSchema type where
> floats are nullable which is working fine, so my problem doesn't seem to
> be related to that.
NULLs bug is already fixed in 1.8.8.
I have no real solution for Your problem atm , but it segfaults when we
list PHP objects' properties.
Try to print_r DBA object to see if all properties are correctly assigned.
Piotras
_______________________________________________
user mailing list
user@lists.midgard-project.org
http://lists.midgard-project.org/mailman/listinfo/user -
Re: [midgard-user] Segfault in DM2 edit forms
Fri July 18 2008 11:36:16 UTCPiotr Pokora schrieb:
> Andreas Flack writes:
>> Hi!
>>
>> I tried setting all int and float fields to NOT NULL default 0, but that
>> doesn't mak a difference. Also, I have another MgdSchema type where
>> floats are nullable which is working fine, so my problem doesn't seem to
>> be related to that.
>
> NULLs bug is already fixed in 1.8.8.
> I have no real solution for Your problem atm , but it segfaults when we
> list PHP objects' properties.
> Try to print_r DBA object to see if all properties are correctly assigned.
They all looked fine. The only thing I found strange is that there was a
property called "action" with an empty value. I don't have a property
with that name, so it must get added automatically somewhere.
By playing around a little, I now found the problem: One of the DBA
classes contained a private var. When I changed this to public, the
segfaults for both DBA classes went away (the other class is the child
of the one with the private var). Is that a bug or is it generally not
allowed to add private vars to a DBA class?
Bye,
Andreas
>
> Piotras
> _______________________________________________
> user mailing list
> user@lists.midgard-project.org
> http://lists.midgard-project.org/mailman/listinfo/user
_______________________________________________
user mailing list
user@lists.midgard-project.org
http://lists.midgard-project.org/mailman/listinfo/user -
Re: [midgard-user] Segfault in DM2 edit forms
Fri July 18 2008 12:03:06 UTCAndreas Flack writes:
Hi!
>> Try to print_r DBA object to see if all properties are correctly
>> assigned.
>
> They all looked fine. The only thing I found strange is that there was a
> property called "action" with an empty value. I don't have a property
> with that name, so it must get added automatically somewhere.
Yes, it's base midgard_object property. As well as guid and metadata for
example.
> By playing around a little, I now found the problem: One of the DBA
> classes contained a private var. When I changed this to public, the
> segfaults for both DBA classes went away (the other class is the child
> of the one with the private var). Is that a bug or is it generally not
> allowed to add private vars to a DBA class?
MidCOM 2.8 is not pure PHP5 framework. It was only adopted to run with PHP5.
The same midgard-php bindings. That's why I didn't renamed it to
midgard-php5.
I doubt it can be fixed in 1-8 branch. At least it should work perfectly
with upcoming 1.9 release.
Midgard-php5 there, is pure language bindings.
Piotras
_______________________________________________
user mailing list
user@lists.midgard-project.org
http://lists.midgard-project.org/mailman/listinfo/user
