multiwindow segmentation fault
Wed Jan 15 12:46:00 GMT 2003
On Wed, Jan 15, 2003 at 01:07:46PM +0100, Alexander Gottwald wrote:
> On Wed, 15 Jan 2003, J S wrote:
> > Kensuke,
> > I'm not an expert on gdb but managed to get the following debug info for
> > you. Also in answer to Harold's question I only have one cygwin1.dll.
> > Program received signal SIGSEGV, Segmentation fault.
> > 0x77e8c40c in _libkernel32_a_iname ()
> No. This is not the right point. If the segfault occurs in _libkernel32_a_iname
> you can continue debugging with "c" until another segfault occurs at another
The information given by that backtrace is completely useless since
XWin as well as the Cygwin DLL don't contain debugging symbols. The
addresses have no meaning w/o that info. The only interesting fact
in the backtrace is:
#0 0x77e8c40c in _libkernel32_a_iname ()
#1 0x00000001 in ?? ()
At this point, a function at address 1 (obviously a wrong pointer) is called
#2 0x6103f35f in _libkernel32_a_iname ()
from *any* function in the Cygwin DLL
#3 0x6103f38b in _libkernel32_a_iname ()
#4 0x6107b7df in _libkernel32_a_iname ()
#5 0x6107baba in _libkernel32_a_iname ()
#6 0x0043b838 in _size_of_stack_reserve__ ()
which has been called from *any* function in XWin.
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developer mailto:firstname.lastname@example.org
Red Hat, Inc.
More information about the Cygwin-xfree