Bizarre Issues with SQLA Debugger 11.0.1 Build 2405

Running into some Bizarre issues when I run a query in the Query Database 
window while in debug mode.

I'm testing a procedure that is used to duplicate/copy information from one 
project into another project.  I was trying to determine why no rows are 
being returned under this particular scenario.

When I copied the Query into the Query Database window, I started getting 
all these bizarre errors.  Sometimes it's Correlation name 'oc' not found, 
when oc is flatly stated at the end of the query.

Sometimes it's "column name contract_____ind not found".  And that column 
name is NOWHERE in the query.  Another one was something like Syntax Error 
near the (cent sign).  Or Syntax Error near line 9.  Take line 9 out and you 
get the same error again.

My query is clean.  What I find, is that when I back the query down to just 
a few columns, it works just fine.  Add a few more, just fine, add a few 
more, just fine.  Then there is a point where the query window just doesn't 
want to show anymore columns.  Even if it is in the query.  Just never goes 
past a certain point in the result set area.  Then the next time I try to 
run the query, "INSERT BIZARRE ERROR HERE".

I looked at all of the hot fixes past 2405 to see if there were any fixes to 
the debugger.  Lots of fixes to the debugger, but none that referenced an 
issue like this.  I read on one posting where somebody mentioned hidden 
control characters being embedded in the query, so I cleaned the query up 
over in my editor.  STILL GET THESE ERRORS!!

Is there an issue with the Query Database window going nuts when the length 
of the query is longer then "X" characters in length??

Just curious if anybody else has seen this.

TIA for any help.

Jeff Gibson
Intercept Solutions - Sybase SQL Anywhere OEM Partner
Nashville, TN 


0
Jeff
1/13/2011 2:36:35 AM
sybase.sqlanywhere.general 32637 articles. 4 followers. Follow

3 Replies
755 Views

Similar Articles

[PageSpeed] 42

If functions or procedures are getting in-lined then you could be looking
at this bug fix:

        622875 - Mixed case parameter names could cause error "column '%1' 
not found"

In addition, there is a remote possibility this might be related to 
something
that is currently being looked into.  If it is, adding explicit 
project/owner
identifiers to the table reference in the query should work around the 
behaviour.

O.W. it would appear you may be running into more than problem.
Doing request logging on the server should tell you what SQL
text is being transmitted to the server (note there may also be CIS
rewrites as well if proxy tables are involved) and if the server is
throwing the error; or if the issue is coming from the Java client side
code.

I don't believe (at least not yet) that this is a size limitation involved 
here.
Usually the Query Editor is capable of handling tens of thousands of
columns (just tested a 25000+ column select list w\2506) long before
I hit (with ~50000 cols) an out of memory condition (Java Heap being fixed
to a maximum).

The fact you are not getting an 'out of Heap' type error, but syntactical 
ones
(that and the fact you are using specialized symbols; such as '�') I suspect 
this
is a true parsing error and my depend exclusively on the text of your query
and schema.  Adding delimiters and decomposing SQL and looking into
charset aspects of this would be where I would focus next.

HTH

"Jeff Gibson" <jgibson@interceptsolutions.com> wrote in message 
news:4d2e6533$1@forums-1-dub...
> Running into some Bizarre issues when I run a query in the Query Database 
> window while in debug mode.
>
> I'm testing a procedure that is used to duplicate/copy information from 
> one project into another project.  I was trying to determine why no rows 
> are being returned under this particular scenario.
>
> When I copied the Query into the Query Database window, I started getting 
> all these bizarre errors.  Sometimes it's Correlation name 'oc' not found, 
> when oc is flatly stated at the end of the query.
>
> Sometimes it's "column name contract_____ind not found".  And that column 
> name is NOWHERE in the query.  Another one was something like Syntax Error 
> near the (cent sign).  Or Syntax Error near line 9.  Take line 9 out and 
> you get the same error again.
>
> My query is clean.  What I find, is that when I back the query down to 
> just a few columns, it works just fine.  Add a few more, just fine, add a 
> few more, just fine.  Then there is a point where the query window just 
> doesn't want to show anymore columns.  Even if it is in the query.  Just 
> never goes past a certain point in the result set area.  Then the next 
> time I try to run the query, "INSERT BIZARRE ERROR HERE".
>
> I looked at all of the hot fixes past 2405 to see if there were any fixes 
> to the debugger.  Lots of fixes to the debugger, but none that referenced 
> an issue like this.  I read on one posting where somebody mentioned hidden 
> control characters being embedded in the query, so I cleaned the query up 
> over in my editor.  STILL GET THESE ERRORS!!
>
> Is there an issue with the Query Database window going nuts when the 
> length of the query is longer then "X" characters in length??
>
> Just curious if anybody else has seen this.
>
> TIA for any help.
>
> Jeff Gibson
> Intercept Solutions - Sybase SQL Anywhere OEM Partner
> Nashville, TN
> 

0
Nick
1/13/2011 8:26:31 PM
Thanks for the heads up Nick,

I'm in the process of upgrading to the latest EBF.  Once that is up I'll 
test it again and let you know the outcome.

Jeff Gibson
Intercept Solutions - Sybase SQL Anywhere OEM Partner
Nashville, TN

"Nick Elson [Sybase An SAP Company]" <@nick@dot@elson@at@sybase@dot@com@> 
wrote in message news:4d2f5ff7$1@forums-1-dub...
> If functions or procedures are getting in-lined then you could be looking
> at this bug fix:
>
>        622875 - Mixed case parameter names could cause error "column '%1' 
> not found"
>
> In addition, there is a remote possibility this might be related to 
> something
> that is currently being looked into.  If it is, adding explicit 
> project/owner
> identifiers to the table reference in the query should work around the 
> behaviour.
>
> O.W. it would appear you may be running into more than problem.
> Doing request logging on the server should tell you what SQL
> text is being transmitted to the server (note there may also be CIS
> rewrites as well if proxy tables are involved) and if the server is
> throwing the error; or if the issue is coming from the Java client side
> code.
>
> I don't believe (at least not yet) that this is a size limitation involved 
> here.
> Usually the Query Editor is capable of handling tens of thousands of
> columns (just tested a 25000+ column select list w\2506) long before
> I hit (with ~50000 cols) an out of memory condition (Java Heap being fixed
> to a maximum).
>
> The fact you are not getting an 'out of Heap' type error, but syntactical 
> ones
> (that and the fact you are using specialized symbols; such as '�') I 
> suspect this
> is a true parsing error and my depend exclusively on the text of your 
> query
> and schema.  Adding delimiters and decomposing SQL and looking into
> charset aspects of this would be where I would focus next.
>
> HTH
>
> "Jeff Gibson" <jgibson@interceptsolutions.com> wrote in message 
> news:4d2e6533$1@forums-1-dub...
>> Running into some Bizarre issues when I run a query in the Query Database 
>> window while in debug mode.
>>
>> I'm testing a procedure that is used to duplicate/copy information from 
>> one project into another project.  I was trying to determine why no rows 
>> are being returned under this particular scenario.
>>
>> When I copied the Query into the Query Database window, I started getting 
>> all these bizarre errors.  Sometimes it's Correlation name 'oc' not 
>> found, when oc is flatly stated at the end of the query.
>>
>> Sometimes it's "column name contract_____ind not found".  And that column 
>> name is NOWHERE in the query.  Another one was something like Syntax 
>> Error near the (cent sign).  Or Syntax Error near line 9.  Take line 9 
>> out and you get the same error again.
>>
>> My query is clean.  What I find, is that when I back the query down to 
>> just a few columns, it works just fine.  Add a few more, just fine, add a 
>> few more, just fine.  Then there is a point where the query window just 
>> doesn't want to show anymore columns.  Even if it is in the query.  Just 
>> never goes past a certain point in the result set area.  Then the next 
>> time I try to run the query, "INSERT BIZARRE ERROR HERE".
>>
>> I looked at all of the hot fixes past 2405 to see if there were any fixes 
>> to the debugger.  Lots of fixes to the debugger, but none that referenced 
>> an issue like this.  I read on one posting where somebody mentioned 
>> hidden control characters being embedded in the query, so I cleaned the 
>> query up over in my editor.  STILL GET THESE ERRORS!!
>>
>> Is there an issue with the Query Database window going nuts when the 
>> length of the query is longer then "X" characters in length??
>>
>> Just curious if anybody else has seen this.
>>
>> TIA for any help.
>>
>> Jeff Gibson
>> Intercept Solutions - Sybase SQL Anywhere OEM Partner
>> Nashville, TN
>>
> 


0
Jeff
1/14/2011 8:11:14 PM
OK,

Here is where things stand Nick.

I've updated my main development machine to SQLA 11.0.1 Build 2538 as well 
as our development server.

This procedure that handles data duplication for us is failing on an insert 
with a "-6".  I have stopped the procedure in the debugger and I'm testing 
the query from the Query Database window.

I started testing the query again and got the same error again.  I started 
backing out columns until it worked, then I started adding them back.  At 
129 columns in the query, it works just fine.  They are all displayed.  When 
I add the 130th column to the query, I start getting the bizarre errors. 
The first time I got "Syntax error near '.' on line 17".  I removed the 
column.  Tested it.   It worked again.  Put column 130 back in the result 
set and got "Syntax error near 'A' on line 17".

oc.contract_salestax_header_0, - column 129
oc.contract_salestax_header_1 - column 130

I'm seriously at a loss to what is going on here.  Now the problem is I'm 
stuck and I have a deadline fast approaching at the end of next week.  I 
need to know why this procedure is choking in order to move forward.

I would gladly forward the procedure to you if you think it might help.

For the record, I have two columns that are just raw numbers... 
(75751256205278).  I also have about 10 columns that just have null in place 
of a column name, because we're not returning anything in that column.

Any direction would be greatly appreciated!  While you look this over, I'm 
going to look at the request logging and see what is being returned.

Thanks Nick!

Jeff Gibson
Intercept Solutions - Sybase SQL Anywhere OEM Partner
Nashville, TN

"Nick Elson [Sybase An SAP Company]" <@nick@dot@elson@at@sybase@dot@com@> 
wrote in message news:4d2f5ff7$1@forums-1-dub...
> If functions or procedures are getting in-lined then you could be looking
> at this bug fix:
>
>        622875 - Mixed case parameter names could cause error "column '%1' 
> not found"
>
> In addition, there is a remote possibility this might be related to 
> something
> that is currently being looked into.  If it is, adding explicit 
> project/owner
> identifiers to the table reference in the query should work around the 
> behaviour.
>
> O.W. it would appear you may be running into more than problem.
> Doing request logging on the server should tell you what SQL
> text is being transmitted to the server (note there may also be CIS
> rewrites as well if proxy tables are involved) and if the server is
> throwing the error; or if the issue is coming from the Java client side
> code.
>
> I don't believe (at least not yet) that this is a size limitation involved 
> here.
> Usually the Query Editor is capable of handling tens of thousands of
> columns (just tested a 25000+ column select list w\2506) long before
> I hit (with ~50000 cols) an out of memory condition (Java Heap being fixed
> to a maximum).
>
> The fact you are not getting an 'out of Heap' type error, but syntactical 
> ones
> (that and the fact you are using specialized symbols; such as '�') I 
> suspect this
> is a true parsing error and my depend exclusively on the text of your 
> query
> and schema.  Adding delimiters and decomposing SQL and looking into
> charset aspects of this would be where I would focus next.
>
> HTH
>
> "Jeff Gibson" <jgibson@interceptsolutions.com> wrote in message 
> news:4d2e6533$1@forums-1-dub...
>> Running into some Bizarre issues when I run a query in the Query Database 
>> window while in debug mode.
>>
>> I'm testing a procedure that is used to duplicate/copy information from 
>> one project into another project.  I was trying to determine why no rows 
>> are being returned under this particular scenario.
>>
>> When I copied the Query into the Query Database window, I started getting 
>> all these bizarre errors.  Sometimes it's Correlation name 'oc' not 
>> found, when oc is flatly stated at the end of the query.
>>
>> Sometimes it's "column name contract_____ind not found".  And that column 
>> name is NOWHERE in the query.  Another one was something like Syntax 
>> Error near the (cent sign).  Or Syntax Error near line 9.  Take line 9 
>> out and you get the same error again.
>>
>> My query is clean.  What I find, is that when I back the query down to 
>> just a few columns, it works just fine.  Add a few more, just fine, add a 
>> few more, just fine.  Then there is a point where the query window just 
>> doesn't want to show anymore columns.  Even if it is in the query.  Just 
>> never goes past a certain point in the result set area.  Then the next 
>> time I try to run the query, "INSERT BIZARRE ERROR HERE".
>>
>> I looked at all of the hot fixes past 2405 to see if there were any fixes 
>> to the debugger.  Lots of fixes to the debugger, but none that referenced 
>> an issue like this.  I read on one posting where somebody mentioned 
>> hidden control characters being embedded in the query, so I cleaned the 
>> query up over in my editor.  STILL GET THESE ERRORS!!
>>
>> Is there an issue with the Query Database window going nuts when the 
>> length of the query is longer then "X" characters in length??
>>
>> Just curious if anybody else has seen this.
>>
>> TIA for any help.
>>
>> Jeff Gibson
>> Intercept Solutions - Sybase SQL Anywhere OEM Partner
>> Nashville, TN
>>
> 


0
Jeff
1/15/2011 12:29:43 AM
Reply:

Similar Artilces:

Cairo Dock Launcher Issue, Packman Build 2.0.0-11.pm.1
Hi, I'm using Cairo-dock 2.0.0-11.pm.1 where there seems to be a problem in that there is no OK button (was there in 1.6.3) in the modify launcher dialogue box and consequently you cannot alter any of the parameters from the GUI and you cannot save any changes due to there being only a quit button. Has anyone else encountered this problem ? :\ Spec: KDE3.5.10, Suse 11.1, Compiz, Nvidia Blob 7600gt -- Dragon32 ------------------------------------------------------------------------ I can confirm that also happens on openSUSE 11.0 with KDE 3.5.9 and with Gnome...

Upgrade of 11.0.0 to 11.0.1 AND 11.0 EBF's
X86 Update of 11.0.0 to 11.0.1 was released 03 Mar 2009 Update of 11.0.0 to build 1598 was released 23 Apr 2009 Should 11.0.0 to build 1598 be applied to 11.0.1 ? ChuckGo No. EBFs should only be applied against the MR that it is intended. The 1598 EBF is intended for 11.0.0. And EBF for 11.0.1 is pending. - chris Charles.Gogolin@stanleyassociates.com wrote: > X86 > > Update of 11.0.0 to 11.0.1 was released 03 Mar 2009 > > Update of 11.0.0 to build 1598 was released 23 Apr 2009 > > Should 11.0.0 to build 1598 be applied to 11.0.1 ? ...

Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11
Name: Greul, Albert Email: albertdotgreulatgooglemaildotcom Product: Firefox Summary: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11 Comments: Hallo zusammen, habe soeben das Neue update installiert. Seit diesem Zeitpunkt funktioniert die Druckerkommunikation zwischen Laptop und Drucker über mein W-Lan nicht mehr!! Vorher funktionierte alles tadellos. Bitte um Beseitigung des Problems. Es grüßt Sie(noch)freundlich Albert Greul Browser Details: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.11) Gec...

perl debugger+taint mode issue in 5.10.0, 5.10.1 5.12.1, no issue in 5.8.8
--001636832e82416c9f048ce9a23b Content-Type: text/plain; charset=ISO-8859-1 Hi All, I got the scenario where perl debugger with taint mode is failing. I am using below .pm amd .xs file for testing $ cat *Mytest.pm* #!/usr/bin/perl -wT package Mytest; use XSLoader (); BEGIN { XSLoader::load('Mytest'); } BEGIN { XSLoader::load('Mytest'); my $var = defined($0)? UNDEFINE : 1; } sub func_test { glob("check"); return 1; } 1; $ cat *Mytest.xs* #include "EXTERN.h" #include "perl.h" #include "XSUB...

RFI
Hi, Is it worth going to 11.5.1 considering 11.9.2 is out? I'm looking for information about upgrading 11.0.3 to 11.5.1 or 11.9.2 on HP-UX. Looking for advice, tips & tricks, pitfalls, etc I'm also interested in other peoples exeriances with 11.5.1 and 11.9.2 with regaurds to performance, stability, bugs & problems. thanks in advance Andrew. -- The views expressed are those of the author, not necessarily of Innovus Limited. Andrew, When I took the "Powering-up for ASE 11.5" class from Syba...

Build recipe -- HPUX 11.0, Oracle 8.1.7.2 64-bit, perl-5.8.0, DBD -Oracle-1.12
Hi, I spent some considerable time attempting to get DBD::Oracle working and wanted to share the solution in hopes of helping fellow travelers. Here are the details of the environment: HPUX 11.0 Oracle 8.1.7.2 64-bit perl-5.8.0 DBI-1.30 DBD-Oracle-1.12 Using the following HP ANSI C compiler per swlist: B3901BA B.11.02.04 HP C/ANSI C Developer's Bundle for HP-UX 11.00 (S800) Build procedure: * Build Perl taking the defaults except for: * Add "-lcl -lpthread " at the begging of the list in response to the question "What...

Smoke [5.11.0] v5.11.0-17-g28e464f FAIL(XF) netbsd 5.0.1 (i386/1 cpu)
Automated smoke report for 5.11.0 patch 28e464fba839d02f376952199261fc8b7d58a0d8 v5.11.0-17-g28e464f p5netbsd: Intel 686-class (i386/1 cpu) on netbsd - 5.0.1 using cc version 4.1.3 20080704 prerelease (NetBSD nb2 20081120) smoketime 7 hours 52 minutes (average 59 minutes 3 seconds) Summary: FAIL(XF) O = OK F = Failure(s), extended report at the bottom X = Failure(s) under TEST but not under harness ? = still running or test results not (yet) available Build failures during: - = unknown or N/A c = Configure, m = make, M = make (after miniperl), t = ma...

Smoke [5.11.0] v5.11.0-49-g5b7d14f FAIL(XF) netbsd 5.0.1 (i386/1 cpu)
Automated smoke report for 5.11.0 patch 5b7d14ffe3988c7f70fd9dc76be9c44168d17a62 v5.11.0-49-g5b7d14f p5netbsd: Intel 686-class (i386/1 cpu) on netbsd - 5.0.1 using cc version 4.1.3 20080704 prerelease (NetBSD nb2 20081120) smoketime 8 hours 10 minutes (average 1 hour 1 minute) Summary: FAIL(XF) O = OK F = Failure(s), extended report at the bottom X = Failure(s) under TEST but not under harness ? = still running or test results not (yet) available Build failures during: - = unknown or N/A c = Configure, m = make, M = make (after miniperl), t = make te...

Smoke [5.11.0] v5.11.0-54-g68cbce5 FAIL(F) netbsd 5.0.1 (i386/1 cpu)
Automated smoke report for 5.11.0 patch 68cbce50efee2c3ae424cfe29c83b65d5b462b69 v5.11.0-54-g68cbce5 p5netbsd: Intel 686-class (i386/1 cpu) on netbsd - 5.0.1 using cc version 4.1.3 20080704 prerelease (NetBSD nb2 20081120) smoketime 8 hours 24 minutes (average 1 hour 3 minutes) Summary: FAIL(F) O = OK F = Failure(s), extended report at the bottom X = Failure(s) under TEST but not under harness ? = still running or test results not (yet) available Build failures during: - = unknown or N/A c = Configure, m = make, M = make (after miniperl), t = make te...

Smoke [5.11.0] v5.11.0-177-g63d690b FAIL(F) netbsd 5.0.1 (i386/1 cpu)
Automated smoke report for 5.11.0 patch 63d690b1f5b7e4a4f5cefe645e21a96651cbe9c2 v5.11.0-177-g63d690b p5netbsd: Intel 686-class (i386/1 cpu) on netbsd - 5.0.1 using cc version 4.1.3 20080704 prerelease (NetBSD nb2 20081120) smoketime 6 hours 35 minutes (average 49 minutes 29 seconds) Summary: FAIL(F) O = OK F = Failure(s), extended report at the bottom X = Failure(s) under TEST but not under harness ? = still running or test results not (yet) available Build failures during: - = unknown or N/A c = Configure, m = make, M = make (after miniperl), t = m...

Smoke [5.11.0] v5.11.0-187-g8dbe7cf FAIL(F) netbsd 5.0.1 (i386/1 cpu)
Automated smoke report for 5.11.0 patch 8dbe7cf704038839ade17963855cf8bfad0c30a3 v5.11.0-187-g8dbe7cf p5netbsd: Intel 686-class (i386/1 cpu) on netbsd - 5.0.1 using cc version 4.1.3 20080704 prerelease (NetBSD nb2 20081120) smoketime 6 hours 35 minutes (average 49 minutes 23 seconds) Summary: FAIL(F) O = OK F = Failure(s), extended report at the bottom X = Failure(s) under TEST but not under harness ? = still running or test results not (yet) available Build failures during: - = unknown or N/A c = Configure, m = make, M = make (after miniperl), t = m...

Smoke [5.11.0] v5.11.0-74-g9e7c6af FAIL(F) netbsd 5.0.1 (i386/1 cpu)
Automated smoke report for 5.11.0 patch 9e7c6af37d3320462cbceb74b487ade8224b9191 v5.11.0-74-g9e7c6af p5netbsd: Intel 686-class (i386/1 cpu) on netbsd - 5.0.1 using cc version 4.1.3 20080704 prerelease (NetBSD nb2 20081120) smoketime 8 hours 32 minutes (average 1 hour 4 minutes) Summary: FAIL(F) O = OK F = Failure(s), extended report at the bottom X = Failure(s) under TEST but not under harness ? = still running or test results not (yet) available Build failures during: - = unknown or N/A c = Configure, m = make, M = make (after miniperl), t = make te...

Smoke [5.11.0] v5.11.0-221-g704e1b1 FAIL(F) netbsd 5.0.1 (i386/1 cpu)
Automated smoke report for 5.11.0 patch 704e1b1ec3309aeb0e2629c93331ffd4c18c8183 v5.11.0-221-g704e1b1 p5netbsd: Intel 686-class (i386/1 cpu) on netbsd - 5.0.1 using cc version 4.1.3 20080704 prerelease (NetBSD nb2 20081120) smoketime 6 hours 34 minutes (average 49 minutes 20 seconds) Summary: FAIL(F) O = OK F = Failure(s), extended report at the bottom X = Failure(s) under TEST but not under harness ? = still running or test results not (yet) available Build failures during: - = unknown or N/A c = Configure, m = make, M = make (after miniperl), t = m...

Smoke [5.11.0] v5.11.0-231-g8f3d599 FAIL(F) netbsd 5.0.1 (i386/1 cpu)
Automated smoke report for 5.11.0 patch 8f3d5996a665cf70e12a836b95e184e9ab628251 v5.11.0-231-g8f3d599 p5netbsd: Intel 686-class (i386/1 cpu) on netbsd - 5.0.1 using cc version 4.1.3 20080704 prerelease (NetBSD nb2 20081120) smoketime 6 hours 31 minutes (average 48 minutes 55 seconds) Summary: FAIL(F) O = OK F = Failure(s), extended report at the bottom X = Failure(s) under TEST but not under harness ? = still running or test results not (yet) available Build failures during: - = unknown or N/A c = Configure, m = make, M = make (after miniperl), t = m...

Web resources about - Bizarre Issues with SQLA Debugger 11.0.1 Build 2405 - sybase.sqlanywhere.general

Debugger - Wikipedia, the free encyclopedia
... , but its sources remain unclear because it lacks inline citations . Please improve this article by introducing more precise citations. A debugger ...

Debugger - Facebook-Entwickler
Facebook-Entwickler Search Facebook Developers Dokumente Werkzeuge Hilfe Neuigkeiten Anwendungen Anmelden Debugger Startseite › Werkzeuge Input ...

Script Debugger 5.0
Major update to one of my favorite apps of all time. If you dick around with AppleScript, you should have Script Debugger.

Review: 5 memory debuggers for Linux coding
When you're working in Linux, manually debugging memory-related errors can be difficult and time consuming. These five tools can help.

Android Studio 1.2 Reaches Beta, Adds Built-In Decompiler, Inline Debugger Variables, Smarter Formatting ...
When Android Studio v1.1 entered the Stable channel, about 6 weeks ago, the Dev Tools team gave word that v1.2 was already well underway and ...

Review: 5 memory debuggers for Linux coding
As a programmer, I'm aware that I tend to make mistakes and why not? Even programmers are human. Some errors are detected during code compilation, ...

Meet the DeBuggers An attitude adjustment regarding the "Fix" at Healthcare.gov
Let me start off by saying that Healthcare.gov is now working well in most areas of the US. Folks are accessing the site all day, every day, ...

Resolving Nightmare Bugs With Reversible Linux App Debugger
Undo and ARM partner on ARM DS-5 tool suite rapidly resolve nightmare bugs

Bed bugs: A new debugger - The Economist
FEW things destroy the reputation of a high-class hotel faster than bed bugs.

Genuitec Launches Debugger for PhoneGap, Apache Cordova
Genuitec ships GapDebug, a new debugger for developers building PhoneGap and Apache Cordova apps.

Resources last updated: 12/9/2015 3:45:36 PM