eyal@cancol.oz (Eyal Lebedinsky) (05/02/90)
Hello everyone. Well, I tried to only post locally but did not manage. I just did 1.3->1.5.9 upgrade and managed to boot the new system. Looks great. I could not find a doco on how exactly /dev/port should be defined (I use an AT). I think I did it wrong which causes readclock to respond '-q' allways. ls had a minor error (_21 multiple ets, normal asld problem) so I removed the label. For this I libunpacked ls.s then libpacked back. Libpack said the program is too large. so I split ls.x (the unpacked one), packed the parts and 'cat' to get new ls.s. It looked too short but asld ate it. Now ls core dumps 'memory fault' when I use '-l'. The questions here are: is there a problem with doing unpack/pack in parts? I thought the packing was a one to one string replacement. Also, is there a solution to the asld problem like this one? First impression of 1.5 is that it is much faster, also protected mode gave me some extra memory that was lost otherwise. Regards Eyal -- Regards Eyal
charles@sdd.hp.com (Charles Keith) (05/03/90)
In article <365@cancol.oz> eyal@cancol.oz (Eyal Lebedinsky) writes: > >ls had a minor error (_21 multiple ets, normal asld problem) so I removed >the label. For this I libunpacked ls.s then libpacked back. Libpack said the >... > >The questions here are: is there a problem with doing unpack/pack in parts? >I thought the packing was a one to one string replacement. Also, is there a >solution to the asld problem like this one? > Exactly the same problem happened to me. Rather than trying to re-pack ls.s, I just fed the unpacked file to asld (this is allowed). I got rid of the multiple define, but the resulting binary dumped core doing ls -l (other options ran ok). The rogue label _21 seemed to be in the vicinity of the static array char *rwx (also associated with the -l option. hmmm..). I moved it out of the function it was in, and ls compiled and linked and ran ok. Since this problem hasn't been widely reported, I assume it must be an artifact of the 1.2 compiler, since I assume all the gurus are using the 1.3 compiler. In doing all of this, I spent a lot of time looking at the symbol tables for ls, and I was able to learn very little about what gets linked into the executable. Most compiler/linkers will give a pretty good map when asked, minix seems weak in this area. Am I missing something here? Before I fix a problem I like to UNDERSTAND it, and in this case I was reduced to trial and error. Any helpful hints or tutorials out there on DEBUGGING under minix? How can problems like this be handled scientifically? Or do we just sprinkle liberally with printf's, bake and test? -- Charles Keith Hewlett-Packard Co. UUCP: {hplabs|ucsd|hpfcla}!hp-sdd!charles 16399 W. Bernardo Dr. Internet: charles%hp-sdd@hplabs.HP.COM San Diego, CA 92127 Disclaimer: I am not a qualified spokesperson.