Fog RVR

New Message Reply Date view Thread view Subject view Author view

ben++at++vislab.su.edu.au
Wed, 24 May 1995 19:28:12 +1000

It seems that my app is trashing shared memory somewhere.
It dies deep down in pfMalloc. viz:

dbx version 3.19 Nov 3 1994 19:59:46
Core from signal SIGSEGV: Segmentation violation
(dbx) > where
  0 _lmalloc(0x1992a130, 0x18140000, 0x40220443, 0x4) ["amalloc.c":720, 0xfb0e344]
   1 _amalloc(0x1814004c, 0x18140000, 0x198766d0, 0x178) ["amalloc.c":76, 0xfb0eabc]
   2 pfMalloc(nbytes = 360, arena = 0x18140000) ["/d/trees/perf1.2a102.Irix5/perf/lib/libpr/DBG.IRIX5/../../../lib/libpr/mall.c":214, 0x571f5c]
   3 createIsoBar(length = 30, path = 0x19876570) ["/mnt/scratch/ben/performer/weather/DBG/../press.c":1005, 0x457c28]
[ etc ]

The pfmalloc request doesn't seem unreasonable - 360 bytes...

Can anyone suggest a good technique to find the problem?
I tried using:

> Date: Tue, 16 Nov 93 15:59:01 -0800
> From: Jim Helman <jimh++at++surreal.asd.sgi.com>
> [...]
> amallopt(3X) to turn on M_DEBUG so the data structure will be checked
> on every amalloc. Then you start sprinkling your code with pfMallocs
> from the arena until you narrow it down.

But it dumped core on the call to amallopt() !! :-(

tsk!
ben.

PS: No one replied to my previous question about using cvd with performer.

New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:51:30 PDT

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.