opensync-users

[Opensync-users] msynctool discover cores

[Anil <rep...@gm...>]

I am just playing with this for the first time. Do you guys see
anything wrong with this configuration?

Also, anyone have any problems building opensync on Solaris? For some
reason the "cmake -DCMAKE_INSTALL_PREFIX=/usr/local" commands did not
recognize the prefix and it wanted to install things in /lib, /share
etc. I had to go hack the cmake_install files.


vds5@vds5:~% msynctool --discover bb
Segmentation Fault (core dumped)

vds5@vds5:~% pstack core
core 'core' of 20563:   msynctool --discover bb
-----------------  lwp# 1 / thread# 1  --------------------
 fed749ab __lwp_park (8068338, fef364bc, 8047b80) + b
 fed6f172 cond_wait_queue (8068338, fef364bc, 8047b80, 0) + 3b
 fed6f512 cond_wait_common (8068338, fef364bc, 8047b80) + 1df
 fed6f746 _cond_timedwait (8068338, fef364bc, 8047be4) + 51
 fed6f7b1 cond_timedwait (8068338, fef364bc, 8047be4) + 24
 fed6f7ed pthread_cond_timedwait (8068338, fef364bc, 8047be4) + 1e
 fee01217 ???????? (fee010c8, fed6e8db, fee01050, fee01142, fed6f8c1, fed6fab0)
 fed6e40c mutex_lock (815b0000, 11adfc3, 8ec8300, 2ee8186a, 83fffffd, f08b08c4)
 0000e808 ???????? ()
-----------------  lwp# 4 / thread# 4  --------------------
 fed75387 __pollsys (8068798, 1, fe21bf20, 0) + 7
 fed1e94a poll     (8068798, 1, 1) + 52
 feec3132 ???????? (fee010c8, fed6e8db, fee01050, fee01142, fed6f8c1, fed6fab0)
 fed6e40c mutex_lock (815b0000, 11adfc3, 8ec8300, 2ee8186a, 83fffffd, f08b08c4)
 0000e808 ???????? ()
-----------------  lwp# 5 / thread# 5  --------------------
 fed75387 __pollsys (fe10fdf0, 1, fe10fdd0, 0) + 7
 fed1e94a poll     (fe10fdf0, 1, 64, fef363e8) + 52
 fef70284 osync_queue_poll (8070618, 0, fef363e8, fef70303, fef35748,
fe000000) + 3c
 fef703e7 _source_check (8071650, 80770d0, 0, 80770d0) + fb
 fef705f1 _source_dispatch (8071650, 0, 8070618) + 151
 feec1a86 ???????? (feec0867, 0, feec4e92, feec4ea0, feec4ea6, 0)
 feec0827 ???????? (8ec8356, e8, c3815b00, 74f17, 1424748b, 8948068b)
 53c300ff ???????? ()
-----------------  lwp# 6 / thread# 6  --------------------
 fed75387 __pollsys (80687d8, 1, fdffdf20, 0) + 7
 fed1e94a poll     (80687d8, 1, 1) + 52
 feec3132 ???????? (fee010c8, fed6e8db, fee01050, fee01142, fed6f8c1, fed6fab0)
 fed6e40c mutex_lock (815b0000, 11adfc3, 8ec8300, 2ee8186a, 83fffffd, f08b08c4)
 0000e808 ???????? ()
-----------------  lwp# 7 / thread# 7  --------------------
 feeee650 ???????? (0, fdefdbb4, fe5a648c, fdefdc6c, fed9e000, fe000800)
 feeefbd7 ???????? (fdefde48, 1, fe5a648c, fdefdc6c)
 fef50b4f osync_error_set (fdefde48, 1, fe5a648c, 0) + 23
 fe5a2d68 syncml_config_parse_database (fdefde48, fe5a634f, 807a2c8,
fee01472) + 194
 fe5a4c4b syncml_http_server_init (8079538, 807a1f8, fdefde48, 1) + 6e7
 fef7766b osync_plugin_initialize (8079538, 807a1f8, fdefde48,
80710a0, 0, 0) + 23
 fef5530c _osync_client_handle_initialize (fdefde48, fef81098, c,
fef86bfb) + 204
 fef5620f _osync_client_message_handler (80770d0, 80710a0, fef7e6c0,
8070618, 0, fef363e8) + 883
 fef6f1cd _incoming_dispatch (8073880, 0, 8070618) + 191
 feec1a86 ???????? (feec0867, 0, feec4e92, feec4ea0, feec4ea6, 0)
 feec0827 ???????? (8ec8356, e8, c3815b00, 74f17, 1424748b, 8948068b)
 53c300ff ???????? ()
-----------------  lwp# 8 / thread# 8  --------------------
 fed75387 __pollsys (fddfde80, 1, fddfde60, 0) + 7
 fed1e94a poll     (fddfde80, 1, 64, 806efe8) + 52
 fef70284 osync_queue_poll (8070f68, 0, feea1851, fef70303, 0, 0) + 3c
 fef703e7 _source_check (80751c0, 1, feec2881) + fb
 feec2a33 g_main_context_check (8458b1c, 8b34408b, e84c50, 5b000000,
71d1c381, d2850002) + 1be
 ec835356 ???????? ()
-----------------  lwp# 9 / thread# 9  --------------------
 fed75387 __pollsys (8068808, 1, fdcfdf20, 0) + 7
 fed1e94a poll     (8068808, 1, 1) + 52
 feec3132 ???????? (fee010c8, fed6e8db, fee01050, fee01142, fed6f8c1, fed6fab0)
 fed6e40c mutex_lock (815b0000, 11adfc3, 8ec8300, 2ee8186a, 83fffffd, f08b08c4)
 0000e808 ???????? ()
vds5@vds5:~%



vds5@vds5:~% msynctool --showgroup bb
Group: bb
Member 2: syncml-http-server
        Configuration : <?xml version="1.0"?>
<config>
  <!-- username to use. Leave empty to not require a username -->
  <username></username>

  <!-- the password for the username -->
  <password></password>

  <!-- The url that you want the server to listen on. This has to be
set on the mobile as well. example: "/" -->
  <url></url>

  <!-- The port where to listen. This has to be set on the mobile as well. -->
  <port>8080</port>

  <!-- If wbxml is enabled, defines wether the wbxml should use string
tables -->
  <usestringtable>0</usestringtable>

  <!-- Never send ADD command, but send REPLACE (not needed normally) -->
  <onlyreplace>0</onlyreplace>

  <!-- Workaround around for mobile phones which only use local
timestamps and _no_ UTC timestamps! -->
  <onlyLocaltime>0</onlyLocaltime>

  <!-- Sets the maximum allowed size in bytes of incoming messages
(some device need this option set). Example: 10000 -->
  <recvLimit>0</recvLimit>

  <maxObjSize>0</maxObjSize>

  <!-- Contact database -->
  <database>
     <name>Contacts</name>
     <objtype>contact</objtype>
  </database>

  <!-- Calendar database -->
  <database>
     <name>Calendar</name>
     <objtype>event</objtype>
  </database>


  <!-- Note database -->
  <!--
  <database>
     <name>Notes</name>
     <objtype>note</objtype>
  </database>
  -->

</config>

Member 1: file-sync
        Configuration : <?xml version="1.0"?>
<config>
  <directory>
    <path>/home/vds5/sync1</path>
    <objtype>data</objtype>
  </directory>

  <!--

   Field objformat set the object format which should be used to store.
   objformat is optional - by default objformat is "file".

  -->

  <directory>
    <path>/home/vds5/sync1</path>
    <objtype>contact</objtype>
    <objformat>vcard30</objformat>
  </directory>

  <directory>
    <path>/home/vds5/sync1</path>
    <objtype>event</objtype>
    <objformat>vevent20</objformat>
  </directory>

</config>

Re: [Opensync-users] msynctool discover cores

[jijun yu <Jij...@Su...>]

Anil wrote:
> I am just playing with this for the first time. Do you guys see
> anything wrong with this configuration?
>
> Also, anyone have any problems building opensync on Solaris? For some
> reason the "cmake -DCMAKE_INSTALL_PREFIX=/usr/local" commands did not
> recognize the prefix and it wanted to install things in /lib, /share
> etc. I had to go hack the cmake_install files.
>   
It should be cmake -DCMAKE_INSTALL_PREFIX:PATH=/usr/local
>
> vds5@vds5:~% msynctool --discover bb
> Segmentation Fault (core dumped)
>
> vds5@vds5:~% pstack core
> core 'core' of 20563:   msynctool --discover bb
> -----------------  lwp# 1 / thread# 1  --------------------
>  fed749ab __lwp_park (8068338, fef364bc, 8047b80) + b
>  fed6f172 cond_wait_queue (8068338, fef364bc, 8047b80, 0) + 3b
>  fed6f512 cond_wait_common (8068338, fef364bc, 8047b80) + 1df
>  fed6f746 _cond_timedwait (8068338, fef364bc, 8047be4) + 51
>  fed6f7b1 cond_timedwait (8068338, fef364bc, 8047be4) + 24
>  fed6f7ed pthread_cond_timedwait (8068338, fef364bc, 8047be4) + 1e
>  fee01217 ???????? (fee010c8, fed6e8db, fee01050, fee01142, fed6f8c1, fed6fab0)
>  fed6e40c mutex_lock (815b0000, 11adfc3, 8ec8300, 2ee8186a, 83fffffd, f08b08c4)
>  0000e808 ???????? ()
> -----------------  lwp# 4 / thread# 4  --------------------
>  fed75387 __pollsys (8068798, 1, fe21bf20, 0) + 7
>  fed1e94a poll     (8068798, 1, 1) + 52
>  feec3132 ???????? (fee010c8, fed6e8db, fee01050, fee01142, fed6f8c1, fed6fab0)
>  fed6e40c mutex_lock (815b0000, 11adfc3, 8ec8300, 2ee8186a, 83fffffd, f08b08c4)
>  0000e808 ???????? ()
> -----------------  lwp# 5 / thread# 5  --------------------
>  fed75387 __pollsys (fe10fdf0, 1, fe10fdd0, 0) + 7
>  fed1e94a poll     (fe10fdf0, 1, 64, fef363e8) + 52
>  fef70284 osync_queue_poll (8070618, 0, fef363e8, fef70303, fef35748,
> fe000000) + 3c
>  fef703e7 _source_check (8071650, 80770d0, 0, 80770d0) + fb
>  fef705f1 _source_dispatch (8071650, 0, 8070618) + 151
>  feec1a86 ???????? (feec0867, 0, feec4e92, feec4ea0, feec4ea6, 0)
>  feec0827 ???????? (8ec8356, e8, c3815b00, 74f17, 1424748b, 8948068b)
>  53c300ff ???????? ()
> -----------------  lwp# 6 / thread# 6  --------------------
>  fed75387 __pollsys (80687d8, 1, fdffdf20, 0) + 7
>  fed1e94a poll     (80687d8, 1, 1) + 52
>  feec3132 ???????? (fee010c8, fed6e8db, fee01050, fee01142, fed6f8c1, fed6fab0)
>  fed6e40c mutex_lock (815b0000, 11adfc3, 8ec8300, 2ee8186a, 83fffffd, f08b08c4)
>  0000e808 ???????? ()
> -----------------  lwp# 7 / thread# 7  --------------------
>  feeee650 ???????? (0, fdefdbb4, fe5a648c, fdefdc6c, fed9e000, fe000800)
>  feeefbd7 ???????? (fdefde48, 1, fe5a648c, fdefdc6c)
>  fef50b4f osync_error_set (fdefde48, 1, fe5a648c, 0) + 23
>  fe5a2d68 syncml_config_parse_database (fdefde48, fe5a634f, 807a2c8,
> fee01472) + 194
>  fe5a4c4b syncml_http_server_init (8079538, 807a1f8, fdefde48, 1) + 6e7
>  fef7766b osync_plugin_initialize (8079538, 807a1f8, fdefde48,
> 80710a0, 0, 0) + 23
>  fef5530c _osync_client_handle_initialize (fdefde48, fef81098, c,
> fef86bfb) + 204
>  fef5620f _osync_client_message_handler (80770d0, 80710a0, fef7e6c0,
> 8070618, 0, fef363e8) + 883
>  fef6f1cd _incoming_dispatch (8073880, 0, 8070618) + 191
>  feec1a86 ???????? (feec0867, 0, feec4e92, feec4ea0, feec4ea6, 0)
>  feec0827 ???????? (8ec8356, e8, c3815b00, 74f17, 1424748b, 8948068b)
>  53c300ff ???????? ()
> -----------------  lwp# 8 / thread# 8  --------------------
>  fed75387 __pollsys (fddfde80, 1, fddfde60, 0) + 7
>  fed1e94a poll     (fddfde80, 1, 64, 806efe8) + 52
>  fef70284 osync_queue_poll (8070f68, 0, feea1851, fef70303, 0, 0) + 3c
>  fef703e7 _source_check (80751c0, 1, feec2881) + fb
>  feec2a33 g_main_context_check (8458b1c, 8b34408b, e84c50, 5b000000,
> 71d1c381, d2850002) + 1be
>  ec835356 ???????? ()
> -----------------  lwp# 9 / thread# 9  --------------------
>  fed75387 __pollsys (8068808, 1, fdcfdf20, 0) + 7
>  fed1e94a poll     (8068808, 1, 1) + 52
>  feec3132 ???????? (fee010c8, fed6e8db, fee01050, fee01142, fed6f8c1, fed6fab0)
>  fed6e40c mutex_lock (815b0000, 11adfc3, 8ec8300, 2ee8186a, 83fffffd, f08b08c4)
>  0000e808 ???????? ()
> vds5@vds5:~%
>
>
>
> vds5@vds5:~% msynctool --showgroup bb
> Group: bb
> Member 2: syncml-http-server
>         Configuration : <?xml version="1.0"?>
> <config>
>   <!-- username to use. Leave empty to not require a username -->
>   <username></username>
>
>   <!-- the password for the username -->
>   <password></password>
>
>   <!-- The url that you want the server to listen on. This has to be
> set on the mobile as well. example: "/" -->
>   <url></url>
>
>   <!-- The port where to listen. This has to be set on the mobile as well. -->
>   <port>8080</port>
>
>   <!-- If wbxml is enabled, defines wether the wbxml should use string
> tables -->
>   <usestringtable>0</usestringtable>
>
>   <!-- Never send ADD command, but send REPLACE (not needed normally) -->
>   <onlyreplace>0</onlyreplace>
>
>   <!-- Workaround around for mobile phones which only use local
> timestamps and _no_ UTC timestamps! -->
>   <onlyLocaltime>0</onlyLocaltime>
>
>   <!-- Sets the maximum allowed size in bytes of incoming messages
> (some device need this option set). Example: 10000 -->
>   <recvLimit>0</recvLimit>
>
>   <maxObjSize>0</maxObjSize>
>
>   <!-- Contact database -->
>   <database>
>      <name>Contacts</name>
>      <objtype>contact</objtype>
>   </database>
>
>   <!-- Calendar database -->
>   <database>
>      <name>Calendar</name>
>      <objtype>event</objtype>
>   </database>
>
>
>   <!-- Note database -->
>   <!--
>   <database>
>      <name>Notes</name>
>      <objtype>note</objtype>
>   </database>
>   -->
>
> </config>
>
> Member 1: file-sync
>         Configuration : <?xml version="1.0"?>
> <config>
>   <directory>
>     <path>/home/vds5/sync1</path>
>     <objtype>data</objtype>
>   </directory>
>
>   <!--
>
>    Field objformat set the object format which should be used to store.
>    objformat is optional - by default objformat is "file".
>
>   -->
>
>   <directory>
>     <path>/home/vds5/sync1</path>
>     <objtype>contact</objtype>
>     <objformat>vcard30</objformat>
>   </directory>
>
>   <directory>
>     <path>/home/vds5/sync1</path>
>     <objtype>event</objtype>
>     <objformat>vevent20</objformat>
>   </directory>
>
> </config>
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> _______________________________________________
> Opensync-users mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensync-users
>   

Re: [Opensync-users] msynctool discover cores

[Anil <rep...@gm...>]

Sorry for the double post re the same problem. I am a little bit tired.
:)

I cleaned up the build and recompiled. Still, msynctool core dumps
when I try to do a discover. Any ideas?



On Jan 8, 2008 9:15 PM, jijun yu <Jij...@su...> wrote:
> Anil wrote:
> > I am just playing with this for the first time. Do you guys see
> > anything wrong with this configuration?
> >
> > Also, anyone have any problems building opensync on Solaris? For some
> > reason the "cmake -DCMAKE_INSTALL_PREFIX=/usr/local" commands did not
> > recognize the prefix and it wanted to install things in /lib, /share
> > etc. I had to go hack the cmake_install files.
> >
> It should be cmake -DCMAKE_INSTALL_PREFIX:PATH=/usr/local
>
> >
> > vds5@vds5:~% msynctool --discover bb
> > Segmentation Fault (core dumped)
> >
> > vds5@vds5:~% pstack core
> > core 'core' of 20563:   msynctool --discover bb
> > -----------------  lwp# 1 / thread# 1  --------------------
> >  fed749ab __lwp_park (8068338, fef364bc, 8047b80) + b
> >  fed6f172 cond_wait_queue (8068338, fef364bc, 8047b80, 0) + 3b
> >  fed6f512 cond_wait_common (8068338, fef364bc, 8047b80) + 1df
> >  fed6f746 _cond_timedwait (8068338, fef364bc, 8047be4) + 51
> >  fed6f7b1 cond_timedwait (8068338, fef364bc, 8047be4) + 24
> >  fed6f7ed pthread_cond_timedwait (8068338, fef364bc, 8047be4) + 1e
> >  fee01217 ???????? (fee010c8, fed6e8db, fee01050, fee01142, fed6f8c1, fed6fab0)
> >  fed6e40c mutex_lock (815b0000, 11adfc3, 8ec8300, 2ee8186a, 83fffffd, f08b08c4)
> >  0000e808 ???????? ()
> > -----------------  lwp# 4 / thread# 4  --------------------
> >  fed75387 __pollsys (8068798, 1, fe21bf20, 0) + 7
> >  fed1e94a poll     (8068798, 1, 1) + 52
> >  feec3132 ???????? (fee010c8, fed6e8db, fee01050, fee01142, fed6f8c1, fed6fab0)
> >  fed6e40c mutex_lock (815b0000, 11adfc3, 8ec8300, 2ee8186a, 83fffffd, f08b08c4)
> >  0000e808 ???????? ()
> > -----------------  lwp# 5 / thread# 5  --------------------
> >  fed75387 __pollsys (fe10fdf0, 1, fe10fdd0, 0) + 7
> >  fed1e94a poll     (fe10fdf0, 1, 64, fef363e8) + 52
> >  fef70284 osync_queue_poll (8070618, 0, fef363e8, fef70303, fef35748,
> > fe000000) + 3c
> >  fef703e7 _source_check (8071650, 80770d0, 0, 80770d0) + fb
> >  fef705f1 _source_dispatch (8071650, 0, 8070618) + 151
> >  feec1a86 ???????? (feec0867, 0, feec4e92, feec4ea0, feec4ea6, 0)
> >  feec0827 ???????? (8ec8356, e8, c3815b00, 74f17, 1424748b, 8948068b)
> >  53c300ff ???????? ()
> > -----------------  lwp# 6 / thread# 6  --------------------
> >  fed75387 __pollsys (80687d8, 1, fdffdf20, 0) + 7
> >  fed1e94a poll     (80687d8, 1, 1) + 52
> >  feec3132 ???????? (fee010c8, fed6e8db, fee01050, fee01142, fed6f8c1, fed6fab0)
> >  fed6e40c mutex_lock (815b0000, 11adfc3, 8ec8300, 2ee8186a, 83fffffd, f08b08c4)
> >  0000e808 ???????? ()
> > -----------------  lwp# 7 / thread# 7  --------------------
> >  feeee650 ???????? (0, fdefdbb4, fe5a648c, fdefdc6c, fed9e000, fe000800)
> >  feeefbd7 ???????? (fdefde48, 1, fe5a648c, fdefdc6c)
> >  fef50b4f osync_error_set (fdefde48, 1, fe5a648c, 0) + 23
> >  fe5a2d68 syncml_config_parse_database (fdefde48, fe5a634f, 807a2c8,
> > fee01472) + 194
> >  fe5a4c4b syncml_http_server_init (8079538, 807a1f8, fdefde48, 1) + 6e7
> >  fef7766b osync_plugin_initialize (8079538, 807a1f8, fdefde48,
> > 80710a0, 0, 0) + 23
> >  fef5530c _osync_client_handle_initialize (fdefde48, fef81098, c,
> > fef86bfb) + 204
> >  fef5620f _osync_client_message_handler (80770d0, 80710a0, fef7e6c0,
> > 8070618, 0, fef363e8) + 883
> >  fef6f1cd _incoming_dispatch (8073880, 0, 8070618) + 191
> >  feec1a86 ???????? (feec0867, 0, feec4e92, feec4ea0, feec4ea6, 0)
> >  feec0827 ???????? (8ec8356, e8, c3815b00, 74f17, 1424748b, 8948068b)
> >  53c300ff ???????? ()
> > -----------------  lwp# 8 / thread# 8  --------------------
> >  fed75387 __pollsys (fddfde80, 1, fddfde60, 0) + 7
> >  fed1e94a poll     (fddfde80, 1, 64, 806efe8) + 52
> >  fef70284 osync_queue_poll (8070f68, 0, feea1851, fef70303, 0, 0) + 3c
> >  fef703e7 _source_check (80751c0, 1, feec2881) + fb
> >  feec2a33 g_main_context_check (8458b1c, 8b34408b, e84c50, 5b000000,
> > 71d1c381, d2850002) + 1be
> >  ec835356 ???????? ()
> > -----------------  lwp# 9 / thread# 9  --------------------
> >  fed75387 __pollsys (8068808, 1, fdcfdf20, 0) + 7
> >  fed1e94a poll     (8068808, 1, 1) + 52
> >  feec3132 ???????? (fee010c8, fed6e8db, fee01050, fee01142, fed6f8c1, fed6fab0)
> >  fed6e40c mutex_lock (815b0000, 11adfc3, 8ec8300, 2ee8186a, 83fffffd, f08b08c4)
> >  0000e808 ???????? ()
> > vds5@vds5:~%
> >
> >
> >
> > vds5@vds5:~% msynctool --showgroup bb
> > Group: bb
> > Member 2: syncml-http-server
> >         Configuration : <?xml version="1.0"?>
> > <config>
> >   <!-- username to use. Leave empty to not require a username -->
> >   <username></username>
> >
> >   <!-- the password for the username -->
> >   <password></password>
> >
> >   <!-- The url that you want the server to listen on. This has to be
> > set on the mobile as well. example: "/" -->
> >   <url></url>
> >
> >   <!-- The port where to listen. This has to be set on the mobile as well. -->
> >   <port>8080</port>
> >
> >   <!-- If wbxml is enabled, defines wether the wbxml should use string
> > tables -->
> >   <usestringtable>0</usestringtable>
> >
> >   <!-- Never send ADD command, but send REPLACE (not needed normally) -->
> >   <onlyreplace>0</onlyreplace>
> >
> >   <!-- Workaround around for mobile phones which only use local
> > timestamps and _no_ UTC timestamps! -->
> >   <onlyLocaltime>0</onlyLocaltime>
> >
> >   <!-- Sets the maximum allowed size in bytes of incoming messages
> > (some device need this option set). Example: 10000 -->
> >   <recvLimit>0</recvLimit>
> >
> >   <maxObjSize>0</maxObjSize>
> >
> >   <!-- Contact database -->
> >   <database>
> >      <name>Contacts</name>
> >      <objtype>contact</objtype>
> >   </database>
> >
> >   <!-- Calendar database -->
> >   <database>
> >      <name>Calendar</name>
> >      <objtype>event</objtype>
> >   </database>
> >
> >
> >   <!-- Note database -->
> >   <!--
> >   <database>
> >      <name>Notes</name>
> >      <objtype>note</objtype>
> >   </database>
> >   -->
> >
> > </config>
> >
> > Member 1: file-sync
> >         Configuration : <?xml version="1.0"?>
> > <config>
> >   <directory>
> >     <path>/home/vds5/sync1</path>
> >     <objtype>data</objtype>
> >   </directory>
> >
> >   <!--
> >
> >    Field objformat set the object format which should be used to store.
> >    objformat is optional - by default objformat is "file".
> >
> >   -->
> >
> >   <directory>
> >     <path>/home/vds5/sync1</path>
> >     <objtype>contact</objtype>
> >     <objformat>vcard30</objformat>
> >   </directory>
> >
> >   <directory>
> >     <path>/home/vds5/sync1</path>
> >     <objtype>event</objtype>
> >     <objformat>vevent20</objformat>
> >   </directory>
> >
> > </config>
> >
> > -------------------------------------------------------------------------
> > Check out the new SourceForge.net Marketplace.
> > It's the best place to buy or sell services for
> > just about anything Open Source.
> > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> > _______________________________________________
> > Opensync-users mailing list
> > Ope...@li...
> > https://lists.sourceforge.net/lists/listinfo/opensync-users
> >
>
>

Re: [Opensync-users] msynctool discover cores

[Daniel G. <dg...@su...>]

On Wednesday 09 January 2008 06:57:17 Anil wrote:
> :)
>
> I cleaned up the build and recompiled. Still, msynctool core dumps
> when I try to do a discover. Any ideas?

Could you build OpenSync additionally with:

 -DCMAKE_BUILD_TYPE=Debug

or RelWithDebInfo if it isn't already...

Re: [Opensync-users] msynctool discover cores

[Anil <rep...@gm...>]

http://pastebin.com/m64e40dbe

The file plugin works, but not the syncml plugin.
Also, if I set the trace environment variables as suggested on some of
the site, it cores even more. Apparently, it has problems getting from
the environment:


vds5@vds5:~% export OSYNC_TRACE=~
vds5@vds5:~% export SYNCML_TRACE=~

vds5@vds5:~% msynctool --discover bb 1
Segmentation Fault (core dumped)
vds5@vds5:~% cat Thread1-29330.log
[1199894110.586501]     >>>>>>>  main(4, 8047d90)
[1199894110.586688]             >>>>>>>  osync_group_env_new(8047d5c)
[1199894110.586723]             <<<<<<<  osync_group_env_new: 8068e00
[1199894110.586754]             >>>>>>>  osync_format_env_new(8047d5c)
[1199894110.586779]             <<<<<<<  osync_format_env_new: 8067fc0
[1199894110.586816]             >>>>>>>  osync_plugin_env_new(8047d5c)
[1199894110.586841]             <<<<<<<  osync_plugin_env_new: 8068780


Without those env variables, I can do "bb 1" but not "bb 2". Something
wrong with this syncml plugin I guess?





On Jan 9, 2008 12:58 AM, Daniel Gollub <dg...@su...> wrote:
> On Wednesday 09 January 2008 06:57:17 Anil wrote:
> > :)
> >
> > I cleaned up the build and recompiled. Still, msynctool core dumps
> > when I try to do a discover. Any ideas?
>
> Could you build OpenSync additionally with:
>
>  -DCMAKE_BUILD_TYPE=Debug
>
> or RelWithDebInfo if it isn't already...
>
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> _______________________________________________
> Opensync-users mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensync-users
>

Re: [Opensync-users] msynctool discover cores

[Daniel G. <dg...@su...>]

On Mittwoch 09 Januar 2008, Anil wrote:
> The file plugin works, but not the syncml plugin.
> Also, if I set the trace environment variables as suggested on some of
> the site, it cores even more. Apparently, it has problems getting from
> the environment:
>
>
> vds5@vds5:~% export OSYNC_TRACE=~
> vds5@vds5:~% export SYNCML_TRACE=~

Oh, you had _TRACE files enabled?

Unfortunately, a lot of code of our codebase is lacking in one very 
fundamental issue, at least i wasn't aware of it. We have lot's of debugging 
output which includes char pointers which might be NULL. This is wrong, and 
make a lot of pain on Solaris, since libc of Solaris will dereferences this 
NULL pointer (and cause the crash). I wasn't aware of this issue, since i 
only got i touch so far with glibc, anyway it's just bad coding of me and 
just wrong. I'll try to clean this mess up the next days... sorry about that. 
Could you try in meanwhile to preload /usr/lib/0@0.so.1

Jijun Yu, applied  once a big patch which fixed several places in OpenSync 
where those debug output might contain a NULL char pointer.. i reverted it, 
for three reason: i had no idea, i'm just dumb and last but not least i 
wanted to have clean solution instead of tons of mini-ifs in every debug 
statement. I thought about a customized xprintf function (sqlite is using for 
debugging output also an customized one which is portable), or just remove 
unneeded/obsolete debug statements which might include NULL char pointer.

If you're interested what this is all about you might check:
http://technopark02.blogspot.com/2006/04/solaris-null-pointer-bugs-usrlib00so1.html

best regards,
Daniel

Re: [Opensync-users] msynctool discover cores

[Anil <rep...@gm...>]

I am making some progress with LD_PRELOAD.

test@test:~% msynctool --discover test 2
ERROR: Object Fomrat "" of a database not set

I am using the default configuration for syncml-http-server.



On Jan 9, 2008 10:57 AM, Daniel Gollub <dg...@su...> wrote:
> On Mittwoch 09 Januar 2008, Anil wrote:
> > The file plugin works, but not the syncml plugin.
> > Also, if I set the trace environment variables as suggested on some of
> > the site, it cores even more. Apparently, it has problems getting from
> > the environment:
> >
> >
> > vds5@vds5:~% export OSYNC_TRACE=~
> > vds5@vds5:~% export SYNCML_TRACE=~
>
> Oh, you had _TRACE files enabled?
>
> Unfortunately, a lot of code of our codebase is lacking in one very
> fundamental issue, at least i wasn't aware of it. We have lot's of debugging
> output which includes char pointers which might be NULL. This is wrong, and
> make a lot of pain on Solaris, since libc of Solaris will dereferences this
> NULL pointer (and cause the crash). I wasn't aware of this issue, since i
> only got i touch so far with glibc, anyway it's just bad coding of me and
> just wrong. I'll try to clean this mess up the next days... sorry about that.
> Could you try in meanwhile to preload /usr/lib/0@0.so.1
>
> Jijun Yu, applied  once a big patch which fixed several places in OpenSync
> where those debug output might contain a NULL char pointer.. i reverted it,
> for three reason: i had no idea, i'm just dumb and last but not least i
> wanted to have clean solution instead of tons of mini-ifs in every debug
> statement. I thought about a customized xprintf function (sqlite is using for
> debugging output also an customized one which is portable), or just remove
> unneeded/obsolete debug statements which might include NULL char pointer.
>
> If you're interested what this is all about you might check:
> http://technopark02.blogspot.com/2006/04/solaris-null-pointer-bugs-usrlib00so1.html
>
> best regards,
> Daniel
>
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> _______________________________________________
> Opensync-users mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensync-users
>