🚀 go-pugleaf

In article <1992Dec29.210927.23562@research.nj.nec.com> max@ccrl.nj.nec.com (Maximilian Ott) writes:
>....For reasons
>beyond my understanding dbx crashes with 

Ok, I got that solved (dbxtool picked up the wrong dbx)

>As a crude debugging hack I put a printf as first statement into
>(xraster.c)Raster::poke 

This was very optimistic and shows that I pretty much don't know what
I'm doing :)

>..
>.... write col: 205 of: 256
>...... Raster::poke
>...... poked!
>.... write col: 206 of: 256
>Segmentation fault (core dumped)

I still get the same problem but now I compiled xraster.c with -g and
single stepped it. It turns out that the 205@0 call corrupts r->image_
when calling XPutPixel. I looked at the definition of XPutPixel and
have really no idea what this is doing. I tried a hack where I saved
and restored r->image_ between calls to XPutPixel but, of course, this
only delays the crash.

The funny thing is that when using the saber debugger it works. 

Still clueless,

max



-- 
Max Ott                 max@ccrl.nj.nec.com         phone: (609)951-2469
NEC C&C Research        Princeton, NJ, 08540        fax:   (609)951-2499