Project

General

Profile

Bug #32

Type mismatch: wanted Integer, got Null instead.

Added by Anonymous about 9 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
fixed

Description

I've had the following error message several times now.

This applications has raised an unexpected error and must abort.

r6 Type mismatch: wanted Integer, got Null instead.
Ping.Ping_Kill.98

error.jpg (13.7 KB) error.jpg Anonymous, 04/09/2010 09:33 AM
1

History

#1 Updated by rdnzl about 9 years ago

Hi, that's strange, it seems that the .Tag of the ping process is empty, this should hold the Id of the ping device.

iId = LAST.Tag

How many ping devices do you have in your database, which version of Gambas are you running. Does it reports normal values when it works in between the errors?

#2 Updated by Anonymous about 9 years ago

At the moment I've got 10 different ping devices in the database.
I haven't upgraded to the 2.20 version of Gambas yet to be honest:)

yes, it reports normal values when it works in between the errors.

#3 Updated by rdnzl about 9 years ago

You can add these 2 lines just above END in Ping_Kill() in Ping.module
--
CATCH
Main.WriteDebugLog(("ERROR: Parsing Ping Result: ") & Error.Text & " at " & Error.Where)
--

This will prevent Domotiga to stop when the error occurs.

But it would be nice if you leave it out for a moment and post the contents of LAST.Tag and LAST.Value.

You can get them when you run domotiga from the IDE and when the error occurs just select these 2 variables in Ping.Module with your mouse, you will see the values.

#4 Updated by rdnzl about 9 years ago

Remove the ? from WriteDebugLog above, it was added by the wiki.

#5 Updated by rdnzl over 8 years ago

  • Status changed from New to Closed
  • Resolution set to fixed

Also available in: Atom PDF