>>At 9:13 PM -0400 on 4/29/02, Robert Covington wrote: >> >> >>> >I have had a series of crashes ongoing for over a year. I have no idea >>>what >>>>the offender is. >>>> >>>>It always accompanies an image import...however I have seen the same 3 >>>>instructions when doing non-image operations also. >>>> >>>> >>>>First I see a >>>> >>>>*NOP >>>>DB.L (probably a sic) >>>>I forget the third >>>> >>>>or similar. >>> >>> >>>The Evil Ones are: >>> >>>*NOP 4E71 >>>DBF D0,*-$0002 51C8 FFFC >>>MOVEM.L (A7)+,D0/A0 4CDF 0101 >> >>Get HexEdit, there are OS 9 and OS X versions available. It can >>search and browse data and resource forks. It also comes with full >>source code and projects for Project Builder, CodeWarrior and MPW. >>Oh, and it's free and the source is covered under the Mozilla Public >>license. > >I would prefer something more automatic...didn't know if RP or Jay or >others could whip up something interesting. > >>BTW, does the filesystem busy keep you from doing anything with >>MacsBug? > >I can't create a log, though I can do some basic checks I think. > >>Can you do a stack chain (SC7 or SC6 IIRC) or does MacsBug >>show a label where the crash is, like the name of a fragment or >>function? > >Just says Illegal instruction at _A008 I think. The app name always varies. > >>Also is it the NOP that has the asterisk? > >Yep. > >That's a strange place to >>crash. I haven't used MacsBug in awhile so I might be off. > >It is a living hell. Just killed me a minute ago, again (about 5 times >tonight). Always, these same 3 items show themselves in Macsbug. Only a >restart will salvage anything. > >Goes away for weeks, then comes up again and ruins my life for a while. > >rc I got to thinking...Norton Disk Editor... Found all 3 of those in sequential Hex on my drive...Says the 'owning file' is Bad Block Extants. I have no idea how to go from there, or if there are other areas. ?? rc