soni.trilok at gmail
Feb 18, 2008, 5:56 AM
Post #4 of 4
(780 views)
Permalink
|
|
Re: D-Bus running on ARM Platform (ERROR: Couldn't connect to session bus)
[In reply to]
|
|
Hi Juha,
On Feb 18, 2008 11:23 AM, Juha Kuikka <juha.kuikka[at]gmail.com> wrote:
> Hi Trilok,
>
> I found on that it is a compiler problem by reading the assembler it
> generates from the C-code. I started suspecting it when a values of a struct
> were different on caller and callee.
>
> Problem was caused by a struct copy in the style:
>
> void function( struct foo *parameter)
> {
> struct foo local_foo;
>
> local_foo = *parameter;
> ...
> }
>
> I had to hastily work around the problem by doing the copy with inline
> assembler. Replacing it with memcpy did not help as compiler optimized it
> into inline copy as well.
>
> Additionally disabling optinizations in compile (-O0) also fixed it.
>
> I don't remember the GCC version we worked with.
Thanks for the reply. My GCC version is 3.4.6 with glibc-2.3.6. Your
suggested trick to disable optimization worked for me :). So, looks
like my toolchain is buggy somewhere in code generation. Now session
bus is working on board under normal user, and also dbus-monitor
executed from this normal user account is able to connect to this
session bus.
But session bus started from the "root" account, doesn't allow to
connect clients from the normal user, looks like some permission
issues of socket file, I will check this in more details.
Thanks again for great help.
--
--Trilok Soni
_______________________________________________
maemo-developers mailing list
maemo-developers[at]maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers
|
