Optimizing and debugging code

This question was posted in response to the following article: http://help.adobe.com/en_US/dreamweaver/cs/using/WSc78c5058ca073340dcda9110b1f693f21-7ba2a .html

Yeah, exactly. This process is moronic. I could have a page with thousands of lines of code and one unbalanced tag. Their solution is for me to take a week to click, scroll to the end of the highlighted section, reclick, scroll some more, and so on.
Check for balanced tags
Open the document in Code view.
Place the insertion point in the nested code you want to check.
Select Edit > Select Parent Tag.The enclosing matching tags (and their contents) are selected in your code. If you keep selecting Edit > Select Parent Tag, and your tags are balanced, eventually Dreamweaver will select the outermost html and /html tags.

Similar Messages

MSI X99S Gaming 7 and debug code 67

Hi,
I have MSI X99S Gaming 7 motherboard, Crucial 2x8GB 2133 DDR4, MSI GTX970 Gaming 4G, Corsair RM650, i7-5820k setup.
When I am trying to boot the machine it always stops and the debug led shows code 67. I have tried to take everything out, reseated processor and to boot with just the minimum set of components. Result is always the same code 67.
I am running out of ideas. Do you have any hints or should I just return the mobo and processor?
Best Regards,
juha

Quote from: shadow85 on 22-December-14, 19:40:31
So are you going to RMA the board or just use it with 2 sticks? Thats means you are not planning on using it in quad channel, would be a waste.
Anyways if I were you I would definatly RMA it asap. This error 67 problem people are having seems to be widespread. MSI really need to look into this.
As has been said previously, contact MSI. Should they look into it? Yes, but the moderators here are not MSI employees, and while we can bring issues to their attention, we cannot make them look into problems.
So if you have this problem, please contact MSI directly: >>How to contact MSI.<<

MSI x99 Gaming 7 Debug code 04

hi this day my computer dont start only black screen , i see mobo debug code 04
msi x99 gaming 7 service manuel say 04 code = Power on South Bridge Initialization
i use 2. bios swich computer working no problem
now i go RMA?
edit: me try bios clear button nothing always full black screen and debug code 04 , i cant remove bios battery 2 graphic card + water cooling :/

If you familiar with flashing bios, you can try use the second bios to recover the first one.
Manuel has some guide...
BIOS recovery with AFUDOS command
When BIOS updating fails or causes the computer non-bootable, you can recover the
failed BIOS by the steps below.
Preparation:
1. Prepare a bootable USB flash drive.
2. Download the latest BIOS file from the MSI official website at www.msi.com, and
then decompress the file.
3. Copy the AFUDE238.exe and the BIOS file to the bootable USB flash drive
BIOS recovery steps:
1. Power off the computer.
2. Set the Multi-BIOS switch to the functional BIOS ROM.
3. Insert the bootable USB flash drive you have made to the USB port.
4. Boot the computer into the bootable USB flash drive.
5. Set the Multi-BIOS switch to the failed BIOS ROM.
6. Execute the below command to flash the BIOS:
For example: AFUDE238 EXXXXIMS.XXX
7. Restart the computer after the BIOS flashing is complete.
Important
Do not use the Multi-BIOS switch when system is booting up.

9C and A2 Debug Codes

Hello a few days ago i turned on my computer and in the bottom right these two digit debug codes appeared i thought everything was normal but when i got up to the windows 8.1 login screen my screen went black but i could see the cursor i backed my files up (Long Story) and reformatted my HDD and re installed windows and ever since then i and still receiving these to debug codes i tried to find them in the Manual but i could not find them. Ever since then i have realized i have been getting LOTS of error on my computer when installing programs and my computer not running to it fullest. So i was wondering if anyone here could help me. I have also reset the CMOS and also booting my computer takes alot longer now.
Thank You in Advanced
My Specs:
CPU: i5 4440 Quad Core 3.1 Ghz
Motherboard: Z87 GD-65 Gaming Motherboard (Socket LGA 1150)
Graphics: AMD Radeon HD 6800 Series
Ram: Corsair Vengeance 8 GB
PSU: FSP Aurum 750 W Gold Power (Modular)
HDD: Seagate Barracuda 1 TB

I had 9C a few times when i had a USB Sata Dock plugged in and turned on after working on some hard drives and shutting down and coming back the next day booting up i got a long pause on 9C... I unplugged the dock and rebooted and it was back to normal boot speed and no issues.
The A2 code could be a few things, but do you have optical drives? AKA CD or DVD drives? Is there a disc in either of them? I left a disc in one of my drives one time and it hung on A2 and took forever to boot, i think if it detects a disc in the drive it checks to see if its a bootable disc and causes the hang. Since i randomly leave a disc in there now and then, i hate optical drive use compared to flash drives but its a necessary evil for dealing with customers sometimes, i went into the BIOS and changed the boot order so that my SSD is first and and made sure everything else is either disabled or after the SSD in the boot order. You can always tap F12 on boot to get to the optical drive if needed to boot, although i generally boot anything i need other then windows from flash drives, including windows installation.
The A2 could also be a problem with the SSD... Do you have it plugged into one of the White 6gb Sata ports? Thats where it should be if you don't. If none of this fixes it and your still booting slow and the SSD is under warranty i would check with the manufacturer. I have had a few bum SSD's that worked great for a bit then suddenly had issues.
Also make sure the firmware on your SSD is the latest! But back up before you try to update it if its not, because i have had firmware updates corrupt the SSD and then had to reinstall windows after that.

Z97 Gaming 5 Debug Codes 41, 42, 43, and 44

Just built my first PC and I am having issues with it.
I have it plugged into a monitor and it does not display anything but I am getting codes on debug codes on the motherboard.
My build is below in case it helps.
CPU: Intel Core i7-4790K 4.0GHz Quad-Core Processor
CPU Cooler: Cooler Master Hyper 212 EVO 82.9 CFM Sleeve Bearing CPU Cooler
Motherboard: MSI Z97-GAMING 5 ATX LGA1150 Motherboard
Memory: G.Skill Ripjaws X Series 8GB (2 x 4GB) DDR3-1600 Memory
Storage: Western Digital Caviar Green 1TB 3.5" 5400RPM Internal Hard Drive
Video Card: MSI GeForce GTX 970 4GB Twin Frozr V Video Card
Case: Thermaltake Level 10 GT Snow Edition ATX Full Tower Case
Power Supply: EVGA SuperNOVA 1000G2 1000W 80+ Gold Certified Fully-Modular ATX Power Supply
Optical Drive: *LG UH12NS30 Blu-Ray Reader, DVD/CD Writer
Operating System: Microsoft Windows 8.1 (OEM) (64-bit)
Like the subject said I am getting a few error codes.
It starts at the lower numbers than sticks around for a bit eventually moving to the higher ones and seems to cap at 44.
Any help on this issue would be immensely appreciated.
Also as a side note I have checked the users manual error code listings but it doesn't seem to contain these specific codes. If I am wrong on this could you tell me where on the manual it lists these?
Thank you very much for your time.

Quote from: brettrodie on 22-March-15, 04:26:05
I get visual output when I unplug my video card.
When entering the boot menu and selecting UEFI: Built-In EFI Shell I get the following
EFI: Shell version 2.31 [4.655]
Current running mode 1.1.2
Device mapping table
blk0 :BlockDevice - Alias (null)
PCiRoot(0x0)/PCi(0x1f,0x2)/Sata(0x0,0x0)
blk1 :BlockDevice - Alias (null)
PCiRoot(0x0)/PCi(0x1f,0x2)/Sata(0x0,5x0)
Press ESC in 1 seconds to skip startup.nsh, any other key to continue
Shell>
Doesn't matter what I press it doesn't do anything
Entering setup instead of the EFI shell takes me to MSi's click bios 4
When I enter the board explorer it shows all the components that I have plugged in as running.
I am at a complete loss to what I need to do to install updates, OS, and to get my video card working.
listed above sounds correct
you need to boot from a bootable device who contain your OS installation disk to proceed with OS install.
about your Video card
when you install it, in which slot is placed?
and have you connected your display to it after that? [not to onboard GPU]
and have you attached all power cables for it?

Debug codes and black screen on boot

I restarted my computer and the debug code on the motherboard says "99"
I also get a black screen on boot up and it does not advance. In the bottom right of the screen is the same "99"
What is the problem. Thanks in advance.
I have the MSi Military Class II 990FXA-GD80

Quote from: badboy2k on 21-August-12, 11:35:53
ok so from that id suspect mainly that your Graphics card may be the cause! what graphics card/s are you using?
I am using the ASUS HD 6670

990FXA-GD80V2 Debug Code "FF" and What it Means.

So my uncle stopped by today and said that his 990FXA-GD80V2 wouldn't post and I asked him if he went through the usual checks like re-seating the graphics card, resetting the CMOS, and trying only 1 memory module. He had done all that and no post, he then told me that he got a debug code of FF on the readout.
So I thought I would search the web and see what I could find out. "Nothing".
So I contacted MSI USA Technical Support and the technician let me know that "FF" Means no system input "Power".
If you get the "FF" code, try removing power and re-seating both the 24pin (Main) and 8pin (CPU) power connectors, if you have another power supply try that. Also check the CPU for any damaged pins.
If neither of those two options work, the board comes with a 3 year warranty and you should send it in for RMA. (Directly to MSI, not reseller).
If this has been posted somewhere else, my apologies, but I did search for it.

Thanks for the report, I think we saw a bad cpu do this as well but most often a bad bios.
Someone had told me it was actually supposed to be for future use, but each time it comes up, it isn't good.

MSI Z77 MPower - Boot issues (A2 debug code and more)

Hey guys,
I've been trying to get my new computer build working but I have encountered several issues when trying to boot the computer.
Before putting everything inside my case, I tested the motherboard + CPU + 1 stick of ram to make sure everything was working. I had issues in the past where I had to remove everything once I had things mounted.
Everything seemed to work and I got into the BIOS and looked like everything was good.
I mounted it in the case with the same configuration and I was able to get into the BIOS again. So I thought everything must be ok.
Fast forward a couple hours later after I finish plugging everything in, I try to turn it on but it just gets into this boot loop.
Turn on > Fans spin for a couple seconds > turns off > repeat. This just kept going on and on and I wasn't exactly sure what was going on.
I started to unplug components and when I only had the Mobo + CPU + 2 sticks of ram in I was able to get into the BIOS.
I plugged things in one at a time and when I plugged in my SSD it would work.. but when I added another drive I would start getting the A2 Debug message on my board.
I would continually get this A2 debug message and I am not sure what to do to get it to work.
I have updated my BIOS to the latest ones and it is still not working.
Could this be an issue with my PSU? I really hope it's not the MOBO..
My System:
i7 3770k
CoolerMaster 212 Evo
MSI M77 MPower
16GB DDR3 Ram
7870PCS+ Tahiti LE
Corsair HX650 PSU

Quote
I've tested it with one stick and 2 SSDs and it doesn't give me the A2 debug code.
Do you have any different ram to test with?
What ram exactly are you using?
You may perhaps be able to set the ram timings in bios to JEDEC standard 9-9-9-24 1600 perhaps

Debugging Code in Beta 2

Hello;
We're currently trying to do some performance analysis of an application on
BEA WLS 6.0 Beta 2 that makes heavy use of MDBs, and new EJB 2.0 Entity Bean
features. We're starting to get some interesting numbers back from JProbe.
Before we go into the analysis of the JProbe results too deeply, I wonder if
you could enumerate for us where in WLS 6.0 Beta 2 you still have
non-optimized debugging code. This will allow us to "temporary disregard"
these areas, or at the very least, not panic, if the performance seems less
than we would expect.
Brian.

Yes, I suspect the separate jar files are your problem. WL 6 optimizes
RMI calls within an application, but calls across applications are much
more expensive.
As a first step, I would deploy the session and entity bean in the same
jar file.
-- Rob
Brian Dueck wrote:
>
Let's start with the basic scenario. We're implementing an active objects
pattern using MDBs, with the state of the active objects stored in EBs. All
this action is shielded from the client through a session bean "controller".
Here's the sequence of operations that we go through (simplified of course):
1. A client application invokes a session bean, which in turn creates an
entity bean. After creating the entity bean, the session bean then puts a
message into a non-persistent JMS topic and returns to the client.
2. An MDB picks up the message that was put into JMS by the session bean,
does some work (including updates on the entity bean), and then puts a
message into a non-persisten JMS queue or topic before returning from
onMessage().
3. MDB(s) pick up the message placed in the topic/queue, they do some work,
and then possibly generate more JMS messages. These are in turn processed by
more MDBs and so on and so forth.
In the simplest possible "hello world" variation of the above scenario, it
looks like we're doing pretty poorly performance wise right now. We're
trying to tear the scenario down though and build it back up step by step,
using the WLS 6.0 examples as a reference. For instance, I've been playing
with the ejb20.message example to do some rough throughput measurements for
the types of messages that we're producing/consuming. The modified example
is giving me much better numbers than my "hello world" scenario above - by
2 orders of magnitude actually.
I haven't run out of things to try yet, but am hoping for some advice that
will steer me in the right direction (vs. brute force trial and error...).
One of the things I noticed, is that the "hello world" implementation is
broken up across multiple jar files - any possibility that is causing major
performance issues. I seem to recall another posting indicating this sort of
multi-jar deployment will cause BEA to not be able to optimize calls.
Thanks for any help,
Brian Dueck
"Rob Woollen" <[email protected]> wrote in message
news:[email protected]...
There have been some performance improvements since beta-2.
However, I would be interested in seeing your profile data. We're always
looking to make the product faster.
-- Rob
Brian Dueck wrote:
Hello;
We're currently trying to do some performance analysis of an application
on
BEA WLS 6.0 Beta 2 that makes heavy use of MDBs, and new EJB 2.0 EntityBean
features. We're starting to get some interesting numbers back fromJProbe.
Before we go into the analysis of the JProbe results too deeply, Iwonder if
you could enumerate for us where in WLS 6.0 Beta 2 you still have
non-optimized debugging code. This will allow us to "temporarydisregard"
these areas, or at the very least, not panic, if the performance seemsless
than we would expect.
Brian.

790FX-GD70 not POSTing no debug code all LEDs on

Hi
I have had my 790FX-GD70 for almost the past 2 years and it has given me no real problems. But yesterday whilst playing Fallen Earth, my computer froze so I gave it a restart and it froze during windows start up. At this point I opened my case and watched the debug display and this time it froze during post, can't remember the debug code it froze on. I tried restarting a few more time and it would freezes at different points during post. At this point I remove it from its case and start barebones testing it. If I left it for a time I could get into the bios and go to the hardware monitoring page and look a the tempter of the CPU for it froze. There it reported that the tempter was 34C. Stopped testing it last night and when I turned it one this morning it would not even start to post. When I turn it on all the LEDs on the board turn on even the overclocking LED and the overclocking switch also turns and to turn off the system I have to do a hard switch off and UPS.
I have tried it with a different UPS with no effect, tried a different graphics card with no effect. Also tried with different RAM and no RAM no effect.
Computer secs:
MB: MSi 790FX-GD70
CPU: AMD Phenom 2 X4 955 Black Edition
UPS: Antec TRUEPOWER Quattro 850 watt
RAM: Corsair XMS3 4Gig DDR3 can not remember the speed.
GPU: MSI AMD Radeon R6950 twin Frozr 2
CPU Heat Sink: Cooler Mater Hyper N520
Any help would be great.

Quote from: Svet on 06-May-12, 02:30:14
try with another video card then
Also done that to no effect, currently I don't have a spare CPU that will work on my motherboard. I was hoping that some one has had this problem before because I have never seen my computer start up with all the LEDs on as it starts up. Also the hard drive LED is on constantly even when there is no hard drive plug in.

How can I build and Debug Tomcat 5.5 under Eclipse?

http://jakarta.apache.org/tomcat/tomcat-5.5-doc/building.html
I am doing some rearch on Tomcat and want to build and debug Tomcat5.5 under Eclipse. Originally tomcat is built with ANT, it downloads all components from different CVS and build them together.
I'd like to import Tomcat Source code (only the core components, such as catalina and Coyota, Jasper) and build them with Eclipse Bilder, so I can debug it as a normal JAVA program under DEGUB-View.
Who has such experience and help me? I havd built Jetty under Eclipse, but Tomcat is much more complex.

Help

How to deploy and debug Central Office 13.0.1 Application in Oracle AS

Hi,
Can anybody please explain me how to deploy and debug Central Office 13.0.1 / 13.1.1 Application in Oracle Application Server via Ecllipse IDE.
Please explain this:
1. Run the Oracle Application Server in debug mode from Ecllipse IDE.
2. Deploy the Central Office 13.0.1 into Application Server from Ecllipse IDE and able to debug the code.
3. Restart the Oracle Application Server in debug mode from Ecllipse IDE.
Thanks
SRR

I got the solution

DEBUG code in LR 4.0

My windows installation of LR4 is generating a LrCatalog.log file containg DEBUG messages.
Indicates to me there is some left-over debug code in the executable.
It might run faster without this.
Sample of file
04/08/2012 11:14:28 DEBUG removing item about to be processed from queue: "Add c40-8927_8_9.tif to catalog"
04/08/2012 11:14:28 DEBUG executing "Add c40-8927_8_9.tif to catalog"
04/08/2012 11:23:55 DEBUG immediate execution of "Add c40-8924_5_6.tif to catalog"
04/08/2012 11:23:55 DEBUG removing item about to be processed from queue: "Add c40-8924_5_6.tif to catalog"
04/08/2012 11:23:55 DEBUG executing "Add c40-8924_5_6.tif to catalog"
04/08/2012 12:00:10 DEBUG immediate execution of "Add c41-5206_7_8.tif to catalog"
04/08/2012 12:00:10 DEBUG removing item about to be processed from queue: "Add c41-5206_7_8.tif to catalog"
04/08/2012 12:00:10 DEBUG executing "Add c41-5206_7_8.tif to catalog"
04/08/2012 14:34:52 DEBUG initializing writeAccessQueue
04/08/2012 14:34:52 DEBUG immediate execution of "Add c41-4625_6_7.tif to catalog"
04/08/2012 14:34:52 DEBUG removing item about to be processed from queue: "Add c41-4625_6_7.tif to catalog"
04/08/2012 14:34:52 DEBUG executing "Add c41-4625_6_7.tif to catalog"

Another user just reported this as well:
http://forums.adobe.com/message/4326750
He gave details of where the LrCatalog.log file was located (c:\users\<user>\documents), and with that I could see that I have one too and quickly figure out what's probably going on:
- The logging appears to be initiated by LR itself, not by plugins. It occurred without the presence of a "config.lua" file.
- The logging appears to come from the LR SDK's LrCatalog module, which provides plugins with access to the catalog. For example, these two lines:
03/17/2012 09:50:23 DEBUG initializing writeAccessQueue
03/17/2012 09:50:23 DEBUG immediate execution of "Tag: apply keywords"
correspond to the Any Tag plugin invoking catalog:withWriteAccessDo ("Tag: apply keywords", function). My log file had entries from other plugins that accessed the same SDK method.
- The logging may be disabled in LR 4.1RC. The last entry in my LrCatalog.log file occurred just before I upgraded from LR 4.0 to LR 4.1RC.

Can we debug code in SSIS?

In the Script Editor you can see C# code and VB code (depending what language you use). I can easily add a Breakpoint, but I can't seem to step through the code. I can't hit F11 or F8; I can't click the green arrow (play button) as it's disabled.
How does one go about debugging code in SSIS?
Knowledge is the only thing that I can give you, and still retain, and we are both better off for it.

Thanks everyone. I got rid fo the syntax errors. I added a breakpoint, closed the Script Task, ran the project, and got this.
SSIS package "c:\users\ryan\documents\visual studio 2010\Projects\Integration Services Project3\Integration Services Project3\Package.dtsx" starting.
Error: 0x6 at Script Task: Could not load file or assembly 'Microsoft.VisualStudio.Tools.Applications.Core, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
Error: 0xC0024104 at Script Task: The Execute method on the task returned error code 0x80070002 (Could not load file or assembly 'Microsoft.VisualStudio.Tools.Applications.Core, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its
dependencies. The system cannot find the file specified.). The Execute method must succeed, and indicate the result using an "out" parameter.
Task failed: Script Task
Warning: 0x80019002 at Foreach Loop Container: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (3) reached the maximum allowed (1); resulting in failure. This occurs when the number of
errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.
Warning: 0x80019002 at Package: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (3) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches
the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.
SSIS package "c:\users\ryan\documents\visual studio 2010\Projects\Integration Services Project3\Integration Services Project3\Package.dtsx" finished: Failure.
The program '[2872] DtsDebugHost.exe: DTS' has exited with code 0 (0x0).
Here's the image.
Does this make any sense?
If I edit the script, take off the breakpoint, and re-run the script, I get this.
it looks like the package runs correctly, but it actually doesn't do anything at all!!
Any idea what's going on?
Knowledge is the only thing that I can give you, and still retain, and we are both better off for it.

Plsql_code_type NATIVE and DEBUG true??

Hi,
In the documentation i've read that we can use pl/sql debugging tools for program units compiled for interpreted mode (but NOT for those compiled for native mode).
Then, if i have:
alter session set plsql_code_type=native
alter package my_pkg compile DEBUGWhy can i specify DEBUG? Because it is compiled in native mode, and in native mode we cannot use debugging, isn't it? The last statement shouldn't have cause an error?
Thanks

Roger,
When I says alter session set plsql_code_type=native; it means all subsequent automatic recompilations of that library unit will use native (machine code) compilation. Ok.
After that I says, alter package my_pkg compile DEBUG; it means I am going to compile the package with DEBUG option and DEBUG option says compiler to compile and generate the code for debugger. Here debugger will read the compiled code in native compilation.
There is no error, simply you are going to provide the native compiled code to debugger.
Here one more parameter plays big role :
PLSQL_DEBUG
PLSQL_DEBUG specifies whether or not PL/SQL library units will be compiled for debugging.
Values:
true - PL/SQL library units will be compiled for debugging
false - PL/SQL library units will be compiled for normal execution
When PLSQL_DEBUG is set to true, PL/SQL library units are always compiled INTERPRETED in order to be debuggable.
When the value of this parameter is changed, it has no effect on PL/SQL library units that have already been compiled. The value of this parameter is stored persistently with each library unit.
Regards
Girish Sharma

Optimizing and debugging code

Similar Messages

Maybe you are looking for