Re: First success of building octave development branch(3-3-51+) by MinGW (for me)

[Tatsuro MATSUOKA]

Hello Shai

Thank you for your suggestion.  I can study a lot from this ML!!

The bt (gdb) command results are shown in the following

(gdb) bt
warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.)

warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.)

#0  ?? (warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.)

) at ../../../hg/octave-work/liboctave/Array.h:249
warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.)

warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.)

#1  0x6b9beab3 in gettimeofday ()
   from 
d:\usr\Tatsu\mingwhome\octaves\OctBuild\hg-devel\src\.libs\liboctinterp-3-3-51+.dll
warning: (Internal error: pc 0x22e557 in read in psymtab, but not in symtab.)

warning: (Internal error: pc 0x22e557 in read in psymtab, but not in symtab.)

#2  0x0022e558 in ?? (warning: (Internal error: pc 0x22e557 in read in psymtab, 
but not in symtab.)

)
warning: (Internal error: pc 0x22e557 in read in psymtab, but not in symtab.)

warning: (Internal error: pc 0x95d691f in read in psymtab, but not in symtab.)

warning: (Internal error: pc 0x95d691f in read in psymtab, but not in symtab.)

warning: (Internal error: pc 0x95d691f in read in psymtab, but not in symtab.)

#3  0x095d6920 in ?? (warning: (Internal error: pc 0x95d691f in read in 
psymtab, but not in symtab.)

)
warning: (Internal error: pc 0x95d691f in read in psymtab, but not in symtab.)

warning: (Internal error: pc 0x22ffdf in read in psymtab, but not in symtab.)

warning: (Internal error: pc 0x22ffdf in read in psymtab, but not in symtab.)

warning: (Internal error: pc 0x22ffdf in read in psymtab, but not in symtab.)

#4  0x0022ffe0 in ?? (warning: (Internal error: pc 0x22ffdf in read in psymtab, 
but not in symtab.)

)
warning: (Internal error: pc 0x22ffdf in read in psymtab, but not in symtab.)

#5  0x77be5c94 in msvcrt!_except_handler2 () from C:\WINDOWS\system32\msvcrt.dll
#6  0x6b3c2336 in _fu553___ZNSs4_Rep20_S_empty_rep_storageE (args=...) at
../../../hg/octave-work/src/file-io.cc:2006
#7  0xbaadf00d in ?? ()
#8  0x00000000 in ?? ()
warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.)

(gdb)

*******************
../../../hg/octave-work/src/file-io.cc:  around 2006 
2003: #if defined (HAVE_MKSTEMP)
2004:           int fd = mkstemp (tmp);
2005: #else
2006:           int fd = mkstemps (tmp, 0);
2007: #endif

*** config.log for mkstemp ***************
configure:22963: checking whether mkstemp is declared without a macro
configure:22987: gcc -shared-libgcc -c -g -O2 -I/WinDevTools/include 
-I/GnuWin32/include conftest.c
>&5
conftest.c: In function 'main':
conftest.c:243:10: error: 'mkstemp' undeclared (first use in this function)
conftest.c:243:10: note: each undeclared identifier is reported only once for 
each function it appears
in
configure:22987: $? = 1

****** config.h for HAVE_MKSTEMP *************
/* Define to 1 if you have the `mkstemp' function. */
/* #undef HAVE_MKSTEMP */


*********
The related thread for mkstemp nad mkstemps
http://n4.nabble.com/replace-use-of-mkstemp-in-makeinfo-m-with-tmpnam-fopen-td1652805.html


Regards

Tatsuro
--- Shai Ayal wrote:

> > I have rebuilt the octave without optimizing option (perhaps default option 
> > is -O2 -g?) and
> > ./run-octave -g.
> >
> > (Th latest ChangeLog date of the snapshot is 2010-04-14 )
> >
> > The result is
> > *************************************************************************
> > GNU Octave, version 3.3.51+
> > Copyright (C) 2010 John W. Eaton and others.
> > This is free software; see the source code for copying conditions.
> > There is ABSOLUTELY NO WARRANTY; not even for MERCHANTABILITY or
> > FITNESS FOR A PARTICULAR PURPOSE. For details, type `warranty'.
> >
> > Octave was configured for "i686-pc-mingw32".
> >
> > Additional information about Octave is available at http://www.octave.org.
> >
> > Please contribute if you find this software useful.
> > For more information, visit http://www.octave.org/help-wanted.html
> >
> > Read http://www.octave.org/bugs.html to learn how to submit bug reports.
> >
> > For information about changes from previous versions, type `news'.
> >
> > octave.exe:1> help fplot
> > warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.)
> >
> > warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.)
> >
> >
> > Program received signal SIGSEGV, Segmentation fault.
> > warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.)
> >
> > warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.)
> >
> > warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.)
> >
> > warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.)
> >
> > warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.)
> >
> > ?? (warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.)
> >
> > ) at ../../../hg/octave-work/liboctave/Array.h:249
> > 249    ~Array (void)
> > warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.)
> >
> > Current language: auto
> > The current source language is "auto; currently c++".
> > warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.)
> >
> > warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.)
> >
> > (gdb)
> > *****************************************************************************
> 
> Tatsuro, perhaps you can also send the output of the "bt" gdb command.
> This will tell use where the problem is in the code
> Shai
> 


--------------------------------------
Get the new Internet Explorer 8 optimized for Yahoo! JAPAN
http://pr.mail.yahoo.co.jp/ie8/