This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: seg fault produces stackdump with no stack trace


On Fri, Apr 10, 2009 at 02:28:49PM -0700, Tarmik wrote:
>>I just checked in a fix which should keep the stack trace going even
>>when it finds a return address of zero.
>
>>It will be in the next cygwin snapshot at: http://cygwin.com/snapshots/
>>but be advised that this is a 1.7.x version of Cygwin and there ar
>>changes to the way mounts are handled in this new version as well as
>>other incompatibilies with the current stable 1.5.x series.  So, if you
>>use it, please research the differences by reading the cygwin mailing
>>list archives.
>
>I have similar problem , and I would like to get fix for this.  However
>- I have latest stable cygwin1.dll as v1.5, and trying to replace it
>with v1.7 produces more problems.  Would it be possible to tell me what
>needs to be changed and where - may be we could try to patch v1.5 only
>with that backtrace support, no other changes ?
>
>Or do I somehow upgrade whol cygwin ?

You have to *research the differences* as mentioned in the seven month
old email that you are quoting.

But the good news is that it is easier to research now.  Just read what's
written on the home page at http://cygwin.com/ .

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]