Hello! [Mon, 17 Jan 2005] Antonio Fiol BonnÃn wrote: > With rsbep: > Program received signal SIGSEGV, Segmentation fault. > 0x08048a6f in decode_and_write ( > ec_buf=0x4019a008 > "Ã4\017IÃÂac\233wYÂÃ&ÃNF\023ÃÂ\035f}ÃÃÃl}N\016>\206f&\177ÃÃÂ", > rs_bsize=255, bep_size=1, rs_dsize=223, sum_of_failures=0xbffff7dc, > uncorrectable_failures=0xc0000000, > argv=0xbffffab6 "/home/fiol/dvbackup-0.0.4rj1/rsbep", quiet=0, > verbose=1) > at rsbep.c:104 > 104 if(!quiet && verbose) > fprintf(stderr,"%s: errors corrected: %ld uncorrectable blocks: %ld\r", > (gdb) bt > #0 0x08048a6f in decode_and_write ( > ec_buf=0x4019a008 > "Ã4\017IÃÂac\233wYÂÃ&ÃNF\023ÃÂ\035f}ÃÃÃl}N\016>\206f&\177ÃÃÂ", > rs_bsize=255, bep_size=1, rs_dsize=223, sum_of_failures=0xbffff7dc, > uncorrectable_failures=0xc0000000, > argv=0xbffffab6 "/home/fiol/dvbackup-0.0.4rj1/rsbep", quiet=0, > verbose=1) > at rsbep.c:104 > #1 0x08049889 in main (argc=1075421192, argv=0xbffff994) at rsbep.c:361 > (gdb) >
Ok. I have to think about that.
> >But you get the segmentation fault also with rsbepC?
>
> Yes:
> Program received signal SIGSEGV, Segmentation fault.
> 0x08048a6f in decode_and_write (
> ec_buf=0x4019a008
> "Ã4\017IÃÂac\233wYÂÃ&ÃNF\023ÃÂ\035f}ÃÃÃl}N\016>\206f&\177ÃÃÂ",
> rs_bsize=255, bep_size=1, rs_dsize=223, sum_of_failures=0xbffff7dc,
> uncorrectable_failures=0xc0000000,
> argv=0xbffffab3 "/home/fiol/dvbackup-0.0.4rj1/rsbepC", quiet=0,
> verbose=1)
> at rsbep.c:104
> 104 if(!quiet && verbose)
> fprintf(stderr,"%s: errors corrected: %ld uncorrectable blocks: %ld\r",
> (gdb) bt
> #0 0x08048a6f in decode_and_write (
> ec_buf=0x4019a008
> "Ã4\017IÃÂac\233wYÂÃ&ÃNF\023ÃÂ\035f}ÃÃÃl}N\016>\206f&\177ÃÃÂ",
> rs_bsize=255, bep_size=1, rs_dsize=223, sum_of_failures=0xbffff7dc,
> uncorrectable_failures=0xc0000000,
> argv=0xbffffab3 "/home/fiol/dvbackup-0.0.4rj1/rsbepC", quiet=0,
> verbose=1)
> at rsbep.c:104
> #1 0x08049886 in main (argc=1075421192, argv=0xbffff994) at rsbep.c:361
> (gdb)
> >
> Attached is the log for rsbepC.
> BTW, if I use the debian-package-supplied rsbepC file (in /usr/bin)
> instead, results are somehow different:
Yes. The binaries in the packages are stripped of debugging information.
> Hope that helps...
Yes. One thing though. Can you reproduce that with just null data
(from /dev/zero)?
cat /dev/zero | rsbepC -v | rsbepC -d -v > /dev/null
cat /dev/zero | rsbep -v | rsbep -d -v > /dev/null
cat big-file-collection/* | rsbep -v | rsbep -d -v > /dev/null
Robert.
--
The work [of software development] is becoming far easier (i.e. the tools
we're using work at a higher level, more removed from machine, peripheral
and operating system imperatives) than it was twenty years ago, and because
of this, knowledge of the internals of a system may become less accessible.
We may be able to dig deeper holes, but unless we know how to build taller
ladders, we had best hope that it does not rain much.
-- Paul Licker
signature.asc
Description: Digital signature
