Thanks Razzak! Your suggestion worked.
I did as you suggested plus a couple of additional steps:
1. Backed-up the RBASE registry settings into a .reg file (to save all my
settings to other RBASE components)
2. Ran RBGXE_Default_Settings.exe and restored default settings
3. Edited the RBASE settings .reg file to remove all settings related to
the Trace
4. Applied the edited RBASE .reg file to recover my settings to other RBASE
components
5. Started and tested the Watch Variable settings
It worked!! I now can add and see watch variables again.
I used the Compare-by-Content Tool to figure out what caused the issue (See
attached). It was due to the parameters "Variable Name", "Type", "Value", and
Break On" being set to zero in the registry (they hold the column size values
of for the Watch Variables window) :
[HKEY_CURRENT_USER\Software\R:BASE Technologies\RBGXE\Trace
Window\Variables]
"Variable Panel Width"=dword:0000050a
"Variable Name"=dword:00000000
"Type"=dword:00000000
"Value"=dword:00000000
"Break On"=dword:00000000
"Variables"=hex:00,00,00,00
Resetting to initial default settings sets all of these to x4C or 76 pixels
[HKEY_CURRENT_USER\Software\R:BASE Technologies\RBGXE\Trace
Window\Variables]
"Variable Panel Width"=dword:00000661
"Variable Name"=dword:0000004c
"Type"=dword:0000004c
"Value"=dword:0000004c
"Break On"=dword:0000004c
"Variables"=hex:01,00,00,00,07,00,00,00,53,51,4c,43,4f,44,45
"Visible"=dword:00000001
I have no idea why/how these parameters were corrupted, except that I
encountered a fatal error running RBASE earlier in the day.
Log Name: Application
Source: Application Error
Date: 4/20/2017 9:35:06 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: xxxxxxxxxxxxxxxxxxxad.asu.edu
Description:
Faulting application name: RBGXE.exe, version: 10.0.2.20411, time stamp:
0x2a425e19
Faulting module name: RBGXE.exe, version: 10.0.2.20411, time stamp: 0x2a425e19
Exception code: 0xc0000005
Fault offset: 0x00004e30
Faulting process id: 0xea38
Faulting application start time: 0x01d2b96cee312814
Faulting application path: C:\RBTI\RBGXE\RBGXE.exe
Faulting module path: C:\RBTI\RBGXE\RBGXE.exe
Report Id: 4f1fa385-25e7-11e7-9908-5cf3706d9a79
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event";>
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-04-20T16:35:06.000000000Z" />
<EventRecordID>90484</EventRecordID>
<Channel>Application</Channel>
<Computer>xxxxxxxxxxxxxxxxx.asu.edu</Computer>
<Security />
</System>
<EventData>
<Data>RBGXE.exe</Data>
<Data>10.0.2.20411</Data>
<Data>2a425e19</Data>
<Data>RBGXE.exe</Data>
<Data>10.0.2.20411</Data>
<Data>2a425e19</Data>
<Data>c0000005</Data>
<Data>00004e30</Data>
<Data>ea38</Data>
<Data>01d2b96cee312814</Data>
<Data>C:\RBTI\RBGXE\RBGXE.exe</Data>
<Data>C:\RBTI\RBGXE\RBGXE.exe</Data>
<Data>4f1fa385-25e7-11e7-9908-5cf3706d9a79</Data>
</EventData>
</Event>
- John
John Murnane
Arizona Board of Regents / Arizona State University
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of
A. Razzak Memon
Sent: Thursday, April 20, 2017 12:33 PM
To: [email protected]
Subject: Re: [RBASE-L] - Issue with Trace Debugger and Watch Variables
John,
First, welcome to R:BASE World!
I hope the information shared on this list is valuable to you and to all our
new and young users who have joined since the introduction of R:BASE X and
R:BASE X Enterprise (Version 10).
Looking at you PDF attachment, once all variables are selected to add to Watch
Variable list, they all should be listed. However, to start fresh, follow the
steps below:
01. Close and Exit R:BASE X Enterprise session 02. Run the following file to
restore all default R:BASE X Enterprise settings
C:\RBTI\RBGXE\RBGXE_Default_Settings.exe
03. Start RBGXE and try the TRACE and see what you get
Hope that helps!
Feel free to reach out to me if you have any questions.
Very Best R:egards,
Razzak
At 03:02 PM 4/20/2017, John Murnane wrote:
>I'm new to this list and appreciate all the activity and information
>shared here. Has anyone experienced a problem with the Trace
>debugger not displaying watch variables? I can open the Watch
>Variables Toolbar and I can open and seemingly add watch variables, but
>nothing appears in the "watch Variables Toolbar window (see
>attached). I found registry variables relating to the watch window
>(see below) but nothing pops out as an obvious solution for me. (I
>have been using the trace debugger and successfully viewing watch
>variables for the past several months - It just now stopped working).
--
You received this message because you are subscribed to the Google Groups
"RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to mailto:[email protected].
For more options, visit
https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_d_optout&d=DwIBaQ&c=AGbYxfJbXK67KfXyGqyv2Ejiz41FqQuZFk4A-1IxfAU&r=KR_gqMVV466XdfTuEOPqxWCALmEXow7h6eI9lKsesk0&m=hh_9H0pVF5K354cBrbngv75aL1Wh7gg4IzlWAxzy1g4&s=9bfNnHet8CYLZHFrNu6w5HLVEGDeI20pKoaygIbCbOw&e=
.
--
You received this message because you are subscribed to the Google Groups
"RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
rbase trace registry.pdf
Description: rbase trace registry.pdf
