Valentina Studio crashing on SQL

[Russ Tyndall]

On 6/26/06 8:06 AM, "Steve Albin" <steve at steve-albin.com> wrote:

> 
> On Monday, June 26, 2006 sunshine at public.kherson.ua (Ruslan Zasukhin) wrote:
> 
>> On 6/26/06 6:31 AM, "Steve Albin" <steve at steve-albin.com> wrote:
>> 
>> Hi Steve,
>> 
>> Have you diagnose your db ?
>> 
>> May be = 3 record is bad ?
> 
> Actually Perfs.nSessid does not exist.  Should give empty cursor.  I did a
> diagnose before the SQL and no problems are found.
> 
> I just submitted this to Mantis with a small database that will reproduce the
> problem.  Entry number 1667.
> 
> 
> Steve
 >> 
>>> I am having a very odd problem with Valentina Studio.
>>> 
>>> The following SQL works fine:
>>> 
>>> Select * from Perfs, IssPerfs
>>>     WHERE Perfs.nSessId = 2
>>>     AND Perfs.nPerfId = IssPerfs.nPerfId
>>> 
>>> The following SQL crashes Valentina Studio:
>>> 
>>> Select * from Perfs, IssPerfs
>>>     WHERE Perfs.nSessId = 3
>>>     AND Perfs.nPerfId = IssPerfs.nPerfId
>>> 
>>> There is no value of Perfs.nSessid = 3.  I would expect an empty cursor, but
>>> instead Valentina Studio just crashes and subsequently will not open the
>>> database.  The target database is a V4RB 1.10 database that I allow
>>> Valentina
>>> Studio to convert to V2.
>>> 
>>> I am using Valentina Studio 2.3.  I really don't care if Valentina Studio
>>> works for me, but the real problem is that my V4RB 2.4b13 app is crashing on
>>> the same SQL. 
>> 
>> 

I was able to duplicate Steve's crash in Vstudio 2.3.2 with Steve's test db
on OS X.4.6.  But I was able to use the exact same syntax on one of my own
databases without problem.

Here's the first half-dozen lines of the crash log.

Thread: 0

Exception:  EXC_BAD_ACCESS (0x0001)
Codes:      KERN_PROTECTION_FAILURE (0x0002) at 0x00000000

Thread 0 Crashed:
0   libvshared_fat_release.dylib       0x05e3e078
fbl::Value_Numeric<(unsigned long)9, (fbl::VALUE_CATEGORY)2,
fbl::policyInPlace<fbl::type_traits<unsigned long> > >::CopyFromIndex(void
const*, bool) + 28
1   libvkernel_fat_release.dylib       0x06397000
fbl::Index_NotUnique_Iterator::get_Value(fbl::smart_ptr<fbl::I_Value>) const
+ 72
2   libvkernel_fat_release.dylib       0x06367950
fbl::IndexIterator_Imp::FindForward(fbl::smart_ptr<fbl::I_Value const>,
bool*) + 132
3   libvkernel_fat_release.dylib       0x0600bb84
fbl::Join_Builder_2::DoInnerJoin_IndexedSortMerge_NU() + 408
4   libvkernel_fat_release.dylib       0x0600b72c
fbl::Join_Builder_2::DoInnerJoin_IndexedSortMerge() + 408
5   libvkernel_fat_release.dylib       0x0600af80
fbl::Join_Builder_2::DoInnerJoin() + 228

I also tried dumping it into xml from Valentina Carbon 1.x, then importing
the xml into Vstudio 2.3.2 without success.  I also tried cloning the db
after converting it with Convert_1_2 -- no luck.

I had thought this might be related to some other Vstudio SQL crashes I
recently experienced, but I don't think [guess] so; at least the crash logs
are entirely different.

-- 
Russ Tyndall
Wake Forest, NC