Euphoria Ticket #178: Display variable error in debugger

(Report based on message:112009)

When tracing the following code (which is similar to the original report), typing "?got_data<enter>" results in:

variable name? got_data  - not defined at this point  

Hitting enter to resume shows the correct value for got_data.

with trace 
object got_data = 0 
trace(1) 
got_data &= 0 
? got_data 

Details

Type: Bug Report Severity: Major Category: Tracing/Debugging
Assigned To: mattlewis Status: Fixed Reported Release: 3340
Fixed in SVN #: 3341 View VCS: 3341 Milestone:

1. Comment by DerekParnell Aug 10, 2010

When using the test forum to preview a message I get this ...

Internal Error 
Fatal run-time error: 
c_proc/c_func: bad routine number (-1) 

2. Comment by DerekParnell Aug 10, 2010

Cannot reproduce this. Using SVN 3336 in Windows platform.

3. Comment by mattlewis Aug 10, 2010

Definitely happens for me on Linux in svn:3340.

4. Comment by DerekParnell Aug 10, 2010

On Windows (svn 3340) I'm seeing this ...

 
   15:  object got_data = 0 
   16:  trace(1) 
   17==>got_data &= 0 
   18:  ? got_data 
   19:   
variable name? got_data 
got_data=0 

5. Comment by mattlewis Aug 10, 2010

For completeness, here's what I get (Linux r3340):

 2:  object got_data = 0                                                                                                                                                
 3:  trace(1)                                                                                                                                                           
 4==>got_data &= 0 
 5:  ? got_data   
 
variable name? got_data  - not defined at this point       

6. Comment by mattlewis Aug 10, 2010

Looks like RTLookup() is always returning a null pointer from be_runtime.c:942 on Linux. It appears to be getting the variable name correct...just not finding it. Even after the value has been displayed, a user entered value isn't being found for some reason.

7. Comment by mattlewis Aug 10, 2010

The call to RTLookup() was using a super large value as a stopping point. Changed it to use the actual length of the symbol table as the stopping point and it worked. I don't think this would address the issue in Interwiki link failed for messasge:112009, messasge:112009, however.

Search



Quick Links

User menu

Not signed in.

Misc Menu