List Info

Thread: Re: mediasinkencoder (and others) segmentation fault




Re: mediasinkencoder (and others) segmentation fault
country flaguser name
China
2007-08-23 02:18:03
I once had similar crash with gcc 4.1.2. i seem to remember
the seg fault is caused by standard c++ runtime shared
library. check the /usr/lib/libstdc++*.so, which needs to
match the compiler you are using.

Frank

Meredydd Luff <meredydd.luffgooglemail.com> wrote:
meredyddwmfl2:~/programming/repertoire/producersdk/bin$ gdb
../samples/mediasinkencoder/dbg/mediasinkencoder
GNU gdb 6.6-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public
License, and you are
welcome to change it and/or distribute copies of it under
certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show
warranty" for details.
This GDB was configured as "i486-linux-gnu"...
Using host libthread_db library
"/lib/libthread_db.so.1".
(gdb) run
Starting program:
/home/meredydd/programming/repertoire/producersdk/samples/me
diasinkencoder/dbg/mediasinkencoder
[Thread debugging using libthread_db enabled]
[New Thread -1210402624 (LWP 31786)]
Helix Producer SDK Sample Application
Step 1: Setting up DLL Paths
Step 2: Set up log system
  Log errors and warnings to file (y/n)?: n
[New Thread -1216742512 (LWP 31789)]
[New Thread -1225380976 (LWP 31790)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1210402624 (LWP 31786)]
0xb7c8c707 in CHXTJobSerializer::deserializeJobFromBuffer
()
   from ./tools/encsession.so
(gdb) bt full
#0  0xb7c8c707 in
CHXTJobSerializer::deserializeJobFromBuffer
    () from ./tools/encsession.so
No symbol table info available.
#1  0xb7c913cf in CHXTEncodingJob::ReadFromBuffer ()
   from ./tools/encsession.so
No symbol table info available.
#2  0xb7c95ad5 in CHXTJobFactory::BuildInstanceFromBuffer
()
   from ./tools/encsession.so
No symbol table info available.
#3  0x08049ea2 in CMediaSinkEncoderApp::CreateJob (
    this=0xbf9c1794) at mediasinkencoder.cpp:367
        this = (CMediaSinkEncoderApp *) 0xbf9c1794
        res = 0
#4  0x08049319 in main (argc=1, argv=0xbf9c2134) at
main.cpp:94
        res = 0
        pInput = (class istream *) 0x8061d60
        file = { = {
        encoderApp = {m_pFactory = 0x8062f90, m_pJob = 0x0,
  m_pPreviewHelper = 0x0, m_pFileLogObserver = 0x0,
  m_pEventSink = 0x0, m_pLogSystem = 0x0, m_pEventPin =
0x0,
---Type  to continue, or q  to quit---
  m_pAudioPin = 0x0, m_pVideoPin = 0x0, m_cInput = 0x8061d60,
  m_nStepCount = 2, m_bEncodeAudio = 0, m_bEncodeVideo = 0,
  m_bEncodeEvents = 0, m_bEncodeTwoPass = 0,
  m_szDllPath =
"DT_Plugins=./plugins00DT_Codecs=./codecs00DT_EncSD
K=./tools00DT_Common=./common",
'' , m_RmsessionDLL = 0x8062060,
  _vptr$ = 0x8061a80 }
        szTemp =
"225+&26234t+&217

22200000000H31234200E!&n02)
05", ''
, "+&0020 2200000000020
220n00000025234L30234nx21004b01
003000000000000t00030000000000
262343025z27d27(c)201H27234t(c)
201p2721730250g31234200E(c)201
n20v2400"...


On 8/21/07, Greg Wright  wrote:
> Meredydd Luff wrote:
> > Hi there,
> >
> >     I'm trying to get started with the Producer
SDK on Linux, and have
> > downloaded v11.0 from the website. On attempting
to run any of the
> > sample applications, I get something along the
lines of:
> >
> > meredyddwmfl2:~/programming/repertoire/producersdk/bin$
> > ../samples/mediasinkencoder/dbg/mediasinkencoder
> > Helix Producer SDK Sample Application
> > Step 1: Setting up DLL Paths
> > Step 2: Set up log system
> >   Log errors and warnings to file (y/n)?: n
> > Step 2: 1
> > Segmentation fault
> >
> >
> > This has been reported before[*], when using new
versions of gcc, but
> > these programs were compiled entirely using gcc
and g++ 2.95 (using
> > the gcc-2.95 and g++-2.95 packages under Debian,
and changing the
> > /usr/bin/gcc and /usr/bin/g++ symlinks).
> >
> > I'm doing some good hair-pulling right now - can
anyone help?
>
> If you are compiling them then you should be able to
debug
> them. Can you run it under 'gdb' and see what the stack
trace
> of the crash is? You will need to build debug to do
this. You
> could also get a core dump file and make it available
so that
> others could look at it perhaps.
>
> --greg.
>
>
> >
> > Meredydd
> >
> > [*]
> http://lists.helixcommu
nity.org/pipermail/helix-producer-issues/2004-November/00682
9.html
> >
> > _______________________________________________
> > Helix-producer-dev mailing list
> > Helix-producer-devhelixcommunity.org
> > http://lists.helixcommunity.org/mailman/listi
nfo/helix-producer-dev
>
>

_______________________________________________
Helix-producer-dev mailing list
Helix-producer-devhelixcommunity.org
http://lists.helixcommunity.org/mailman/listi
nfo/helix-producer-dev


       
---------------------------------
Take the Internet to Go: Yahoo!Go puts the Internet in your
pocket: mail, news, photos & more. 
_______________________________________________
Helix-producer-dev mailing list
Helix-producer-devhelixcommunity.org
http://lists.helixcommunity.org/mailman/listi
nfo/helix-producer-dev

[1]

about | contact  Other archives ( Real Estate discussion Medical topics )