Stack memory issue with gstreamer

[jbvulai]

I've did a few more test, most notably on the target device and might have
found some interesting things.
First of all, i've realized that things are much different in here. a lot of
the facts i said earlier were from tests done in my programming environment,
this includes the valgrind massif test and the 5 threads.

The stack with 33x4k pages were from the target device, and after observing
it... it does not show any growth. I've found out that on the target device,
only 2 threads were spawn, the main one and a gstreamer thread. Here's the
interesting part. This is the output of "thread apply all bt" in gdb :

Thread 2 (LWP 9620):
#0  0x40b71384 in ?? () from /lib/libpthread.so.0
#1  0x40b6cff6 in pthread_cond_wait () from /lib/libpthread.so.0
#2  0x40ecd378 in g_cond_wait () from /usr/lib/libglib-2.0.so.0
#3  0x4368b300 in ?? () from /usr/lib/libgstaudio-0.10.so.0
Cannot access memory at address 0x1
#4  0x4368b300 in ?? () from /usr/lib/libgstaudio-0.10.so.0
Cannot access memory at address 0x1
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 1 (LWP 9611):
#0  0x41097276 in ?? () from /lib/libc.so.6
#1  0x411064a8 in poll () from /lib/libc.so.6
#2  0x40e8de90 in ?? () from /usr/lib/libglib-2.0.so.0
Cannot access memory at address 0x0
#3  0x40e8de90 in ?? () from /usr/lib/libglib-2.0.so.0
Cannot access memory at address 0x0
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb)

What do you make of this?



--
View this message in context: http://gstreamer-devel.966125.n4.nabble.com/Stack-memory-issue-with-gstreamer-tp4666681p4666708.html
Sent from the GStreamer-devel mailing list archive at Nabble.com.