Error On My Hyper cam 2

vjfaq · Post by **vjfaq** » Wed Jul 29, 2009 4:58 pm

I have a error message when i open my hyper cam with wine so i used the ubuntu terminal and this is the message that came up.
Thanks

Threads:
process tid prio (all id:s are in hex)
00000008 (D) Z:\data\network_homes\stu9194\Videos\HyCam2.exe
00000009 0 <==
0000000c
0000000e 0
0000000d 0
0000001f
00000020 0
00000035
00000036 0
Backtrace:
=>1 0x7e8789cf ICSeqCompressFrameStart+0xff() in msvfw32 (0x0032dfd8)
2 0x0044057a in hycam2 (+0x4057a) (0x0032e038)
3 0x00000005 (0x00000094)
4 0x00000000 (0x00000000)
stu9194@optiplex960-s-5rnbz1s:~/Videos$

Vincent Povirk · Post by **Vincent Povirk** » Wed Jul 29, 2009 8:37 pm

The backtrace is not useful without debugging symbols.

Also, you should install your program using Wine if you haven't.

--
Vincent Povirk

vjfaq · Post by **vjfaq** » Thu Jul 30, 2009 1:31 am

I have already installed the hypercam with wine.
and wat do u mean by debugging symbols

jorl17 · Post by **jorl17** » Thu Jul 30, 2009 5:26 am

vjfaq wrote:I have already installed the hypercam with wine.
and wat do u mean by debugging symbols

That log you posted is a backtrace, it provides information on 'what was happening'. Specifically, it shows the stack.

When an application is built with Debugging Symbols, it means that it has 'identifiers' and 'names' inside it to help people debugging (seeing what's going on).

You can see (part) of that in a sample of your backtrace:

=>1 0x7e8789cf ICSeqCompressFrameStart+0xff() in msvfw32

As you can see, that part of the backtrace has useful information (the name of a function, in this case: ICSeqCompressFrameStart). It has this info because Wine was compiled with it enabled.

If you could find a version of HyCam2.exe with debugging symbols (which I doubt the author provides, but you never know) it would be useful for others to understand what is going on inside your application. However, it would probably be more useful to get a version of Wine with more debugging info.

Cheers,

Jorl17

austin987 · Post by **austin987** » Thu Jul 30, 2009 10:11 am

On Thu, Jul 30, 2009 at 5:26 AM, jorl17<[email protected]> wrote:

vjfaq wrote:
I have already installed the hypercam with wine.
and wat do u mean by debugging symbols
That log you posted is a backtrace, it provides information on 'what was happening'. Specifically, it shows the stack.

When an application is built with Debugging Symbols, it means that it has 'identifiers' and 'names' inside it to help people debugging (seeing what's going on).

You can see (part) of that in a sample of your backtrace:

=>1 0x7e8789cf ICSeqCompressFrameStart+0xff() in msvfw32

That should have code line numbers in it.

--
-Austin

jorl17 · Post by **jorl17** » Thu Jul 30, 2009 11:11 am

austin987 wrote:On Thu, Jul 30, 2009 at 5:26 AM, jorl17<[email protected]> wrote:
vjfaq wrote:
I have already installed the hypercam with wine.
and wat do u mean by debugging symbols
That log you posted is a backtrace, it provides information on 'what was happening'. Specifically, it shows the stack.

When an application is built with Debugging Symbols, it means that it has 'identifiers' and 'names' inside it to help people debugging (seeing what's going on).

You can see (part) of that in a sample of your backtrace:

=>1 0x7e8789cf ICSeqCompressFrameStart+0xff() in msvfw32
That should have code line numbers in it.

--
-Austin

Precisely why I said:

If you could find a version of HyCam2.exe with debugging symbols (which I doubt the author provides, but you never know) it would be useful for others to understand what is going on inside your application. However, it would probably be more useful to get a version of Wine with more debugging info.