[Xapian-devel] Sample quickstartindex unable to create database on Windows 2008

[Martin Margo]

Thanks for your reply.

C:\tmp\junk14 existed. I deleted the dir and XapianIndex.exe still crashes.


I debugged the program and in database.cc in Xapian code line 205 function 
WritableDatabase::WritableDatabase(const std::string &path, int action) : Database ()

'path' variable is preceeded with weird characters, such as so:
"ÌÌÌÌC:\tmp\junk14"

const std::basic_string<char,std::char_traits<char>,std::allocator<char> > &

While it should have read 'C:\tmp\junk14'. 

Thanks for your help.

Martin





----- Original Message ----
From: Olly Betts <olly at survex.com>
To: Martin Margo <martin_margo at yahoo.com>
Cc: xapian-devel at lists.xapian.org
Sent: Tuesday, June 30, 2009 7:30:09 PM
Subject: Re: [Xapian-devel] Sample quickstartindex unable to create database on  Windows 2008

On Tue, Jun 30, 2009 at 05:08:33PM -0700, Martin Margo wrote:
> My desktop is running Windows 2008 and I used Microsoft Visual Studio
> 2008 to compile 1.0.13 Xapian and Ruby bindings.  I then copy and
> paste this code from xapian website to my new project and link it with
> Xapian lib. Everything builds and links nicely
> 
> http://xapian.org/docs/quickstartindex.cc.html
> 
> I ran it with the following args
> XapianIndex.exe C:\tmp\junk14 "hello hello" hello 
> 
> C:\tmp\junk14 exists and empty.

And is a directory?  You don't need it to exist, but if it exists and is
a file that won't work.

> The app crashed. 
> 
> First-chance exception at 0x7771f328 in XapianIndex.exe: Microsoft C++
> exception: Xapian::DatabaseCreateError at memory location 0x006bf9d8..
> Unhandled exception at 0x7771f328 in XapianIndex.exe: Microsoft C++
> exception: Xapian::DatabaseCreateError at memory location 0x006bf9d8..
> The program '[4800] XapianIndex.exe: Native' has exited with code 0 (0x0).

It seems to have failed to catch the exception, which is pretty broken.
Are you using any unusual compiler options?

And does "simpleindex" in the example work?

> Has anyone encountered this error before? How can I fix it?

Not that I've heard of.

Cheers,
    Olly