Hello Uli, Seems that help printing is too right aligned. My terminal has about 100 chars wide and yet I see a lot of empty chars at the left.
See my other comments inline. Anton Pak > Hi Anton, > as we discussed yesterday in the chat room, here I send you the client > program that I created to work with the oHPI APIs. > The attached archive contains the client and the patch for the Makefile > for your convenience. > > I did only very few tests yet, but found a few issues with the APIs. > - The APIs work only with the default domain. Yes, we have a bug #2986517 "oHPI API does drawback in multi-domain configuration" > - oHpiHandlerInfo, oHpiHandlerGetNext, oHpiHandlerDestroy seem ok. Good! I tried it and it always said there were no handlers at all. > - oHpiHandlerFind always returns invalid session. The same on my side. > This function is the only one that already has a session parameter > (which is needed for other domains) so I think the introduction > of that parameter was not completed at that time. > - oHpiHandlerRetry I didn't test yet. I think it only works when a > handler is defined completely but couldn't initialize or was terminated > for some other reason than oHpiHandlerDestroy. > - oHpiHandlerCreate I couldn't verify yet. It always returns some error. > Since you were able to call it from within the daemon, I think the > parameters are not copied through. I tried it. Parameters were transfered from client to daemon correctly. However there is memory corruption issue: - daemon receives oHpiHandlerCreate request -- daemon creates new config hash table -- daemon fills the table with params (I inserted printf there and saw them ok) -- daemon creates handler -- handler remembers pointer to the config hash table -- daemon destroys config hash table - daemon returns SA_OK as oHpiHandlerCreate response And from this time the created handler contains pointer to deleted table. When I run hpi_shell to see resources the daemon crashes. > - oHpiParamGet and oHpiParamSet for OHPI_DAT_SAVE always runs into the > following error: > ohcontrol: marshal.c:468: Marshal: Assertion `0' failed. > Aborted > other parameters seem to work. Will look into this. > > What say? > > Cheers, > Uli > <<u7130-6.tgz>> > > > > > ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Openhpi-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openhpi-devel
