On Sun, Jan 24, 2010 at 07:42:32AM +, Marco Atzeri wrote:
>Hi,
>recently, after some change in the source, the octave
>development branch started to SIGSEV on exit.
>The strange issue is that this happen only
>for cygwin and not on the other platforms.
>I have not yet found a solution, only a
On 24/01/2010 07:42, Marco Atzeri wrote:
> My question however is about the gdb backtrace, is the
> "Cannot access memory at address 0x1a" at # 9 normal ?
I wouldn't read too much into it. Could indicate that there's some kind of
corruption at the top end of the stack, or it could just be gdb
Brian Keener wrote:
> As to the second part of my question - is there a way to determine what
> sources/debug info I still need to get around the ?? Or is that just a
> matter of tracing from the sources I can see to find what it is bing
> called next?
Most of those frames with ?? are totally bog
Brian Dessent wrote:
> thinking that somehow there's a segmentation fault in pthreads code when
> there isn't. If you're going to enable the option then you need to
> "continue" past those non-faults.
Brian,
Thanks for clarifying that. I was doing that for two reasons - the first
is because I
Brian Keener wrote:
> (gdb) set cygwin-exceptions on
> (gdb) run
> ...
> Program received signal SIGSEGV, Segmentation fault.
> 0x610d5de9 in pthread_mutexattr_init (attr=0x23cb50)
> at /usr/develop/src/src/src/winsup/cygwin/thread.cc:123
> 123 if ((*object)->magic != magic)
> (gdb) thre
5 matches
Mail list logo
