Ticket #798 (new enhancement)

Opened 6 years ago

Last modified 5 years ago

print errors on the osynctool's STDERR instead of only showing them in the traces

Reported by: chi70 Owned by: dgollub
Priority: normal Milestone:
Component: osynctool/msynctool Version: 0.38
Severity: normal Keywords:
Cc: bricks

Description (last modified by felixmoeller) (diff)

as seen in ticket #795 it is difficult for a user to understand whats going wrong as msynctool does not show any errors on the cli but only in the traces

Therefore I suggest to print these errors on the msynctool's STDERR instead of only showing them in the traces,

Change History

comment:1 Changed 6 years ago by bricks

  • Cc bricks added

comment:2 Changed 6 years ago by felixmoeller

  • Description modified (diff)

comment:3 follow-up: ↓ 4 Changed 6 years ago by dgollub

Initial implemention with r3533.

Unfortunatley it's only enabled when also OSYNCTRACE is enabled.... We should make OSYNC_PRINTERROR independent of OSYNC_TRACE.

But OpenSync? build without tracing support should also keep OSYNC_PRINTERROR disabled. Purpose of OSYNC_PRINTERROR is to find "dirty" error handling which have to be fixed...

comment:4 in reply to: ↑ 3 Changed 6 years ago by chi70

Replying to dgollub:

Initial implemention with r3533.

Unfortunatley it's only enabled when also OSYNCTRACE is enabled....

At least with OSYNC_TRACE set it looks really fine!

$msynctool --listplugins
ERROR: Unable to open module /opt/opensync/build/lib/libopensync1/plugins/syncml-plugin.so: /opt/opensync/build/lib/libopensync1/plugins/syncml-plugin.so: undefined symbol: osync_objtype_sink_num_objformats
EXIT_ERROR: osync_module_load: Unable to open module /opt/opensync/build/lib/libopensync1/plugins/syncml-plugin.so: /opt/opensync/build/lib/libopensync1/plugins/syncml-plugin.so: undefined symbol: osync_objtype_sink_num_objformats
Available plugins:
file-sync

$ unset OSYNC_TRACE
$ msynctool --listplugins
Available plugins:
file-sync

Thanks so far.

comment:5 follow-up: ↓ 6 Changed 5 years ago by tuju

see ticket #630

comment:6 in reply to: ↑ 5 Changed 5 years ago by chi70

Replying to tuju:

see ticket #630

#630 has a different target.

I verified with r3822, the behaviour is still the same. With OSYNC_TRACE set it works as expected.

comment:7 Changed 5 years ago by tuju

  • Version changed from 0.36 to 0.38
  • Summary changed from print errors on the msynctool's STDERR instead of only showing them in the traces to print errors on the osynctool's STDERR instead of only showing them in the traces
Note: See TracTickets for help on using tickets.