On Wed, Jan 10, 2007 at 11:21:02AM +0900, Ken'ichi Ohmichi wrote: > > Hi. > > Last year, we discussed about "dumping to a remote host by makedumpfile". > For this feature, I will add 2 options of STDOUT output to makedumpfile. > If this feature is implemented, makedumpfile can output the dump data to > the dump device directly also. > > > The first option "-S": > This option outputs the dump data to STDOUT. > The dump data output by this option is different from normal dumpfile. > Because this option outputs STDOUT with the fileoffsets by each data > instead of lseek(). The analysis tool (ex. crash) can not read this > dump data, and the next option "-R" creates the readable dumpfile from > this dump data. >
I missed the discussion which happened last time. Why there are two options -S and -R? Why can't we generate the final output in one go on standard output? What's the file format of this intermediate file? Should we use -O instead of -S for outputting to standard output. "tar" utility uses -O for extracting output to standard output. > The second option "-R": > This option creates the readable dumpfile from STDIN (the dump data) > output by the option "-S". > What is readable dump file? Readable by crash? Can it be read by gdb? I think you already had provided options for output file type. (One for diskdump format file and other one for ELF header format file). In that case we don't have to create another option -R ? Thanks Vivek _______________________________________________ fastboot mailing list [email protected] https://lists.osdl.org/mailman/listinfo/fastboot
