Re: Segfault in Cactid

Brian Dessent dessent.net> writes: > > Larry Adams wrote: > > > Brian, I am assuming that I can just download the latest cygwin of winsup and > > then configure/make. What configure/make options should I be using to > > incorporate debug symbols? > >

Re: Segfault in Cactid

Larry Adams wrote: > Brian, I am assuming that I can just download the latest cygwin of winsup and > then configure/make. What configure/make options should I be using to > incorporate debug symbols? The default compil

RE: Segfault in Cactid

Original Message >From: Larry Adams >Sent: 02 September 2005 10:48 > Brian Dessent dessent.net> writes: > >> >> Larry Adams wrote: >> >>> So my questions are: How do I trace the memory location above to a >>> known system call using gdb? When, I attach to my hung process, what >>> sho

Re: Segfault in Cactid

Brian Dessent dessent.net> writes: > > Larry Adams wrote: > > > So my questions are: How do I trace the memory location above to a known system > > call using gdb? When, I attach to my hung process, what should I be doing to > > determine the calling/offending function. > > Build a cygwin1.

Re: Segfault in Cactid

Larry Adams wrote: > So my questions are: How do I trace the memory location above to a known > system > call using gdb? When, I attach to my hung process, what should I be doing to > determine the calling/offending function. Build a cygwin1.dll with debug symbols and then use addr2line. Or us