On Mar 16, 2010, at 21:56 , Andreas Jellinghaus wrote: > Am Dienstag 16 März 2010 17:52:37 schrieb Viktor TARASOV: >> For me it's quite useful at the developing stage . >> >> Probably the debug line content can be made configurable? >> I mean to make optional 'pid', 'time', 'process name', 'line', ... > > the complex side would be config file parsing. we could > create a new complex option like > "debug_info = file,line,function,time,pid,process" > and encode that as many small options in the context > or one option with a bit field. > > debug side would be easy to implement. but config wise, > this looks hard. we could instead use many smalls > debug_include_filename = yes/no > debug_include_line = yes/no > debug_include_function = yes/no > ... > but that is ugly I think, but still possible and easier > to implement. That looks ugly and is not necessary as well (we just reduced confusing the errors vs debug log, why make it hairy again?).
Ideally developers run gdb (and maybe some extra defines in the build process) and casual installations generate a consistent debug log, without a way to change it, other than re-compile the software. Remember - many "users" of OpenSC (out of those 500 on one of the mailing lists) are actually software developers to some extent. The rest (several tens of thousands) need to be instructed to send a detailed log, if necessary. -- Martin Paljak http://martin.paljak.pri.ee +3725156495 _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
