[maemo-developers] [maemo-developers] Problems with remote debugging using scratchbox - osso_initialize fails
From: Jon Adams jon.adams at concerttechnology.comDate: Wed Nov 8 00:11:03 EET 2006
- Previous message: [maemo-developers] usbnet/MMC applet
- Next message: [maemo-developers] Problems with remote debugging using scratchbox - osso_initialize fails
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Can anyone suggest a HowTo or provide a simple explanation on running a Maemo application that calls osso_initialize from within the scratchbox environment using the latter's cpu transparency feature? What I mean is running the application on the Nokia 770 device using USB networking and sbrsh -- not on the PC host. I'm trying to produce a workflow for debugging a program remotely using the developer rootfs and a scratchbox environment that uses cpu transparency. Thus, I have a scratchbox set for ARMEL and cpu transparency and I can compile my programs without problems but when I run the program executable from the scratchbox command line the call to osso_initialize always fails. However, if I install the program package on the Nokia it functions correctly and I can also run the executable directly from an ssh session to the Nokia. I've also tried the run-standalone script but that seems to make no improvement/change. I suspect that the problem may be the requirement for the .desktop and .service files that are referenced by osso_initialize/Task Navigator/D-BUS, but how do you set those for remote debugging? Is it even possible? Do I have to remove the calls to osso_* in order to perform remote debugging? I suppose there may also be issues with dynamically linked libraries but that would mean that the cpu transparency feature isn't that transparent (or I misunderstand its capabilities, which is certainly a possibility). I __can__ get remote execution and debuggin working on a simple "Hello World" standard i/o program but are there any special tricks to debug remotely with a Hildon-GUI application? A remote debug workflow example using the sample Maemopad application would be quite useful. Here is my basic setup: Developer rootfs installed on the Nokia with root access enabled (should be the rootfs based upon the first release of OS2006). Host PC running Debian etch with kernel 2.6.17 Scratchbox 0.9.8.8 and cs2005q3.2-glibc toolchains with ARMEL target and cpu transparency enabled with sbrsh. The following command when executed from the scratchbox always fails at osso_initialize: [sbox-ARMEL:~/maemopad/maemopad-1.5/src] > run-standalone.sh ./maemopad This happens whether or not the full maemopad package is installed on the Nokia (i.e. with the package installed the maemopad related .service and .desktop files exist on the Nokia file system). Also, as I mentioned before I can execute a copy of the maemopad executable from an ssh session and the same binary works fine when it is called directly from the Nokia file system. Thus, only when maemopad is launched from the scratchbox does the osso_initialize call fail.
- Previous message: [maemo-developers] usbnet/MMC applet
- Next message: [maemo-developers] Problems with remote debugging using scratchbox - osso_initialize fails
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]