Re: Initialization problem

New Message Reply Date view Thread view Subject view Author view

Bernard Leclerc (bleclerc++at++cae.ca)
Wed, 24 Jul 1996 10:21:09 -0400

On Jul 24, 2:34pm, Axel Schmidt wrote:

> I get a segmentation violation on all our machines.

...

> The stack trace is always the same for all machines:
>
> Core from signal SIGSEGV: Segmentation violation
> (dbx) where
> > 0 pfBuffer::pf_destroyMem(pfMemory*)(0x1000a530, 0x18075d50, 0x5dc08040,
0x0) ["../../../lib/libpf/pfBuffer.C":1377, 0x5ccc464c]
> 1 pfDBase(0x1000a530, 0x18075d50, 0x5dc08040, 0x0)
> ["../../../lib/libpf/pfProcess.C":2994, 0x5cd0d654]
> 2 dbFunc(void*)(0x0, 0x18075d50, 0x5dc08040, 0x0) ["magic.c++":25,
> 0x402c68]
> 3 mpDBase(void)(0x1000a530, 0x18075d50, 0x5dc08040, 0x0)
> ["../../../lib/libpf/pfProcess.C":3093, 0x5cd0da78]
> 4 pfConfig(0x1000a530, 0x18040830, 0x1, 0x0)
> ["../../../lib/libpf/pfProcess.C":1705, 0x5cc9a99c]
> 5 main(0x1000a530, 0x18075d50, 0x5dc08040, 0x0) ["magic.c++":44,
> 0x402d44]
> 6 __start() ["crt1text.s":133, 0x4029fc]
>

Axel, Remi,

I obtain the same result: a SIGSEGV, a core dump, and the same stack trace -
which BTW doesn't make sense at all since the crash supposedly happen in
pfConfig().

So, I tried to run the program under dbx and set a break point to pfFrame(). It
works for five or six frames, then it dies with the following pfNotice:

        Caught SIGCHLD. Exiting due to death of child with pid ...

I noticed the first pfFrame will create the window and call the pfPipeWindow
config function. The second call to pfFrame will generate the following
pfNotice:

        PF Notice: Using 60Hz video rate

Remi,

In a separate mail, I'll send you the executable and the core generated so you
can analyse it.

Thanks.

--
Bernard Leclerc			CAE Electronics Ltd., 8585 Cote De Liesse
Technical Leader		Saint-Laurent, Quebec, Canada, H4L-4X4
3-D Graphics Applications	tel: +1 514 341 2000 extension 2275
bleclerc++at++cae.ca			fax: +1 514 340 5496
=======================================================================
List Archives, FAQ, FTP:  http://www.sgi.com/Technology/Performer/
            Submissions:  info-performer++at++sgi.com
        Admin. requests:  info-performer-request++at++sgi.com

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:53:13 PDT

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