X-Spam-Check-By: sourceware.org From: "Dave Korn" To: Subject: RE: Octave's oct-modules built with gcc-3.4.4-1 crash octave. Date: Tue, 21 Feb 2006 11:54:23 -0000 Message-ID: <00ca01c636dd$8e6342e0$a501a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <01fc01c636db$c229e0e0$9903a8c0@cspc212> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 21 February 2006 11:41, Juhani Saastamoinen wrote: > 4. Running octave with gdb suprisingly causes segmentation fault. > The following happens, of course, indepent of the installed gcc version. > This looks like some subtle problem, maybe with cygwin dll, > octave, or gdb. Skillful people, please investigate, also try to > reproduce and verify the problem. Stack trace is included. > > $ gdb octave > (gdb) run > Starting program: /usr/bin/octave.exe > > Program received signal SIGSEGV, Segmentation fault. > 0x610ae938 in pthread_key_create () from /usr/bin/cygwin1.dll > (gdb) bt > #0 0x610ae938 in pthread_key_create () from /usr/bin/cygwin1.dll False alarm, normally caught by cygwin's error handlers. Try continuing (gdb 'c' command) and see what happens next. cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/