Shocked.. BUG LV 5 - LV 7.1

Shocked.. BUG LV 5 - LV 7.1

Post by Wieb » Thu, 26 Aug 2004 20:01:38


Hi,

Well, I'm shocked... The same bug is still in the newest version (been there
since LV 5, I think).

Try it:

Make a string (constant, control indicator, it doesn't matter).
Type a few lines in it.
Make a selection like this:
go to the nth line
press shift
press the up key
press end
You now have a selection.
Press CTRL-X

LabVIEW 7.1 crashes right away.

For previous versions (note some weird characters created by a pointer
overflow):
Press CTRL-V

This bug has been reported, but it is still there. So I guess you have to
use an event structure to prevent users from using CTRL-X...

Regards,

Wiebe.
 
 
 

Shocked.. BUG LV 5 - LV 7.1

Post by Wieb » Thu, 26 Aug 2004 20:08:36

Just to give the thread a more possitive edge:

D:\lvmerc\src\source\manager\memory.cpp(1704) : DAbort: negative length = -1
in MoveBlock
$Id: //labview/branches/Mercury/dev/source/manager/memory.cpp#10 $
0x00465ED5 - LabVIEW <unknown> + 0
0x004A46DE - LabVIEW <unknown> + 0
0x004A4582 - LabVIEW <unknown> + 0
0x005C5DFB - LabVIEW <unknown> + 0
0x005C6734 - LabVIEW <unknown> + 0
0x00751FA0 - LabVIEW <unknown> + 0
0x009E3859 - LabVIEW <unknown> + 0
0x0074A888 - LabVIEW <unknown> + 0
0x009E3859 - LabVIEW <unknown> + 0
0x0074A439 - LabVIEW <unknown> + 0
0x009E3859 - LabVIEW <unknown> + 0
0x006B9747 - LabVIEW <unknown> + 0
0x00749F3C - LabVIEW <unknown> + 0
0x009E3859 - LabVIEW <unknown> + 0
0x0061AA40 - LabVIEW <unknown> + 0

Regards,

Wiebe.





there

 
 
 

Shocked.. BUG LV 5 - LV 7.1

Post by jpeter » Fri, 27 Aug 2004 14:32:56

Good catch! I will report this to R&D (actually myself) for review.

Jeff Peters
National Instruments
LabVIEW R&D