Lightroom -traceback debugging tip

Excerpt from post by Dan Tull at http://feedback.photoshop.com/photoshop_family/topics/how_to_better_understand_when_lr_bug s_bite_can_we_somehow_activate_logging
To get Lightroom traceback info:
Windows
1. Right click the Lightroom icon you use to launch on the desktop and choose Copy from the menu.
2. Right click the Desktop and choose Paste from the menu.
3. Right click the new icon and choose Properties... from the menu.
4. In the Target field of the properties dialog append -tracebacks (separated from the path by a space):
(It will look like this at the end when you're done (leave the rest of the path alone): lightroom.exe" -tracebacks)
5. In the general tab, you might also want to change the name so you can easily visually distinguish this new icon from the original (we'll delete it when we're done).
6. Go to this site in your browser: http://technet.microsoft.com/en-us/sy...
7. On the right hand side of the page, click the "Run DebugView" link (it's safe – it's just a debug output viewer from Microsoft)
8. Click through the Eula if necessary.
9. With DebugView running, double click the new icon we created in steps 1-5.
10. Repeat the steps in Lightroom that cause the error message or hang that you are seeing.
11. Save the output. You can either highlight and copy/paste or choose "Save as..." from the menu to save the output to a file. Mac
1. In Finder, navigate to the Utilities subfolder of the Applications folder (Command + Shift + U).
2. Double Click Terminal.app
3. Paste the following text: '/Applications/Adobe Lightroom 3.app/Contents/MacOS/Adobe Lightroom 3' -tracebacks
(Note that this may be different for some versions of LR, like RC/Beta releases, etc)
4. Press enter to start.
5. Repeat the steps in Lightroom that cause the error message or hang that you are seeing.
6. Use the Shell -> Export Text As... menu item (Command + S) to save the output to a file (or select it for copy and paste). Note that the output this produces requires the exact build number of LR that emitted it to be translated into a stack trace with source file names and line numbers.
Rob

Hi Raj,
So you declared one Internal table in SE38 and you couldn't see the Internal table at Debugging.
You do One thing. Put Break-point before the Internal table,
For Ex :
Append wa to Itab.
break-point.
Thanks,
Reward If Helpful.

Similar Messages

Debugging Tips for Mapping and Validation modules

Hi,
I am new to CRM, anybody can send the dubuging tips for Mapping and Validation modules and the list of tables which I have to check before loading.
(Intilal load & delta load)
Regards
KHM

KHM,
The first thing you need to make sure is that all queues are deregistered on both systems. Check the settings in SMQR and SMQS on your systems. The next step is that your middleware connection user must be a dialog user in order to debug the middleware properly.
If you have those two steps done, then for an initial load you can actually go into to the queues and debug the entries from each queue. For a delta load you will need to put a break point in the transaction before the middleware trigger, and then turn on update debugging(if you want to go through the full process).
The only other key is looking up the correct function modules for the adapter objects to determine what is being called. Once you know these and have done the steps above you can in general debug.
Validate the information above in your system and then let me know where you are getting stopped in your debug process. We can then try to figure out why the debugger is not being called.
Good luck,
Stephen

Debugging tip

I have a program with multiple loop, with each loop containing a queue state machine. For loop A, it went into state X, and I tried to back trace to see where is the state info enqueued, but I can't find it. The info enqueued should be a particular enum value in a cluster, but ctrl+f didn't help. Any tips on debugging this? Thanks!
Kudos and Accepted as Solution are welcome!

Are either typedefs? Also, how are the queues ID'd? Are they "wired queues" where the queue ref is wired throughout, or are they name queues, where the queues has a defined name. If the later try a ctrlo-F on the name and see where there are instances of calling the queue, where there might be "enqueues".
Putnam
Certified LabVIEW Developer
Senior Test Engineer
Currently using LV 6.1-LabVIEW 2012, RT8.5
LabVIEW Champion

Debugging Tips needed

Hello,
I am new to Flex and trying to get a sample application I
downloaded from the internet working on my local machine.
When I run the application in my web browser I get the login
form made in flex then when I try to log in I get a pop message
with this error inside.
quote:
Data Communication Error
HTTP Request error
The application I downloaded is using SOAP to communicate
with my webserver. How do I debug the flex application in order to
figure out why I am getting this "HTTP Request error"?
Thanks.

Look in the code of the application you downloaded to see
where this error prompt is generated from. The location of that in
the code should give you an idea about what's going wrong.
Given the nature of the message the fault could fall into any
number of categories. You'll need to post a link to the app code if
you want further help.
You can use
Ethereal to tap the wire if you
want to see what the Flash player is doing at a lower level.

Whole screen is not repainted, need debug tips

We are running an application which uses some jogl for animaties.
Sometimes when the animation is finished and we set the GLCanvas to invisible, the normal
java JPanels are not repainted.
Also alt-tab to another windows application and back will not force a redraw.
The application itself is still working, clicking on a (now) not visible button will trigger
the jogl animations, and these are show correctly.
Also from logging it appear that the AWT-thread is not blocking.
We are looking for tips that can help find us the problem from logging
as it only appears a few times a week and it is not reproducable.

The problem is that most of the time it works, but after some hours/days, the java panels are not repainted.
There is no memory leak.
paintComponent is not overwritten, a object is made visible to do the animation.
Pseudo code:
public class AnimateTilePopup extends JPanel {
GLCanvas glCanvas;
public AnimateTilePopup() {
super(null);
setOpaque(true);
glCanvas = new GLCanvas();
glCanvas.setLocation(0,0);
glCanvas.setSize(width, height);
glCanvas.setVisible(false);
glCanvas.setFocusable(false);
add(glCanvas);
flipRendererZoom = new AnimateRendererZoom();
glCanvas.addGLEventListener(flipRendererZoom);
public startAnimation() {
glCanvas.setVisible(true);
this.setVisible(true);
public stopAnimation() {
glCanvas.setVisible(false);
this.setVisible(false);
So sometimes when we call stopAnimation(), the animation is stoppped, but the underlying java JPanels are not repainted.
When we now call startAnimation, the animation is shown and when stopped, no repaint for the normal JPanels.
Most times it is working perfectly, only sometimes it failes.
What can be the cause or what logging can be gather that might gives us a clue how to fix this problem.

Lightroom Windows performance tips

Hey folks
Just thought I'd share a little performance tip: Defragmenting your catalog makes a really big difference. Sure, you could run the Windows Defragmenting tool, which takes care of the whole disk, but that takes forever to run. I use contig, a freebie command line tool from Sysinternal (technet.microsoft.com/en-us/sysinternals/bb897428.aspx) and was surprised at how much it helped. It's also something you can do very quickly: my 200Mb catalog was heavily fragmented and I fixed that in about a minute. I'm pretty sure there are other, more user-friendly tools out there which do the same thing.
My machine is a 2.8GHz P4 (circa 2001) with 2Gb RAM, and I have a 12000+ image catalog in LR. Query speeds are very good, and working with the images is now entirely CPU-limited.
Back to lurking, now ...

Hi Carl,
Can you please log a bug for this.We will investigate the issue.
Thanks,
Asha
Adobe ColdFusion Team.

Cocoa debugging tips?

I'm an experienced programmer working my way through "Cocoa Programming for Mac OS" by Aaron Hillegass. I have a few questions about how the SE process works in Objective C.
1) is there a way to make the compiler catch more syntax errors? I'm not a great typist, and sometimes I mis-type the name of a method. The compiler doesn't catch this, and it comes up as an ugly message at runtime. Is there a way to make the compiler more strict?
2) Where can I find some good techniques on debugging nibs? The bindings seem like a very powerful tool, but if you do something wrong, I'm finding it very hard to track down where the mistake was. For example, I get a "X is not key value coding compliant for the key Y" but I can't figure out why it's trying to USE the Y key of object X.
3) In general the magic code generated by the compiler looks very useful, but, I can imagine that debugging code with a lot of automatically generated methods and method calls is going to be difficult because there's a lot of stuff going on behind the scenes. Is there something I should read to give me an idea of how to track things down in that?
Thanks a lot.

There isn't any easy answer I know of for binding problems other than taking things one step at a time. Turn off the bindings and re-enable them one-by-one until you track down the error. Version control can be handy for this. You do have to be careful with them because they often have side effects and/or an extensive interface that it expects to find.
I find bindings one of the more difficult parts of modern Cocoa to get my mind around. Sometimes, the best answer is to not use them for a while, then come back and try it agin. It may "magically" work the second time after the logic has percolated in your head for a while.
As for debugging, printf isn't the only way to do it. The debugger works fine, much better than it did a couple of years ago. But debugging a large, multithreaded GUI is just difficult. Sometimes, having a powerful logging system is the best way to go about it.
RanjeetJones (né orangekay) actually has it backwards. I use the debugger with my Etresoft programs much more than when I'm working at my "day job". When you have a couple million lines of C++ running on a number of Solaris machines, a debugger really isn't much help. You have to study both the code and the log files. You identify a few places that could be the source of the problem, add some log statements, add some debugging code, and keep running it. On big systems, running the debugger is a last resort because it is so slow to get setup and so tedious to run. Add multiple threads, processes, servers, and a GUI and it gets even worse.
I think studying the code is more useful than running a debugger. Start writing comments. When it gets difficult to explain, you've found a potential problem. Pay close attention to the names of variables and methods. They should be what their name indicates and do what their name says. It sounds like an obvious statement, but good names can help immensely with understanding your own code. I get more benefit out of focusing on variable and method names than probably any other single area.

SUB:Debuging tips

Hi Sdners,
Please tell me debuging techniques in abap and tel me any deatils.
Thanks & regards
sreenu
*Moderator Message: Please search for available information before posting.
Edited by: kishan P on Sep 5, 2010 9:01 PM

The SB Li've card does 0Hz and up; the Logitech x-530 does 40Hz and up, and may have a tendency to behave badly if fed a signal at 35Hz or below. Turning down the low end will certainly fix this. If you have an EQ tool that will give you a 50Hz slider, that will give you a little more low-end than the 64Hz slider does. A 35Hz slider may work also, but might not slope off the 40-and-below steeply enough to "clean out" the signal.
The long-term danger is that over-driving the sub amp at these low frequencies will burn it up. (If it sounds boomy, it's being over-dri'ven.) The fact it's booming at all suggests this is not an amp with a lot of protection circuitry built into it. Personally, I would not put the sub close to anything flammable...
If you have an old, unused stereo you'll do much better by connecting the SB Li've sub out to an aux input on the old amp, turning its tone control off treble and a little up on bass, and listening through whatever old speaker (preferably 8") you have available. That way the tiny little Logitech amp can dri've the satellites and give you 5 channels, while the bigger older stereo handles the bass.
Cheers,Bob

Changes are not updated from ECC to CRM How to debug

Hi,
QCs 1140049726 and 1140047459 were updated in P20 system to remove the WBS. This was done per normal P20 process and instructions. P20 system correctly reflects that QCs have no WBS value and the contracts are BOX - all is correct in P20.
CSP still shows these QCs as having a WBS assigned to them. This is incorrect. It has been over 24 hours since the P20 QCs were changed to reflect no WBS, but CSP still has not been replicated with the correct data.
How to proceed with it. How to debug from ECC to CRM.
Prem.

Hello Prem,
Could you please have a look at SAP note 656823?
This note contains debug tips for btx data transfer. Please check point 6 which talks about the delta download.
Hope this could be helpful.
Best regards,
Maggie

RFC Debugging

Hi Experts,
I have done GOOGLE for How to debug Remote FM. Have found many links and methods of doing so. But unfortunately none of them help me to debug Remote FM.
Links Like :
How to Debug SAP RFC , background job , update FM etc.. &laquo; SAP Ignite
Remote ABAP Debugging
**************** - Tips - Remote ABAP debugging
http://www.sap-help.net/Page/abap-development-getting-started/abap-debugger-setup/abap-debugger-rfc-debugging/
SAP Note 1004248.
Regards,
Sagar

Hi Bhushan,
Thanks for the prompt reply.
I have done steps 1 to 3.
Now for Step 4 do i need to click on Remote Logon button as shown in below screen shot?
If yes, than i did but i have not got any popup or any other screen.
After that i have follow Steps 5 to 7, but at break point it doesn't stop.
Regards,
Sagar

Debug weblogic.properties conversion error

All,
I'm attempting to use the web console application/Convert weblogic.properties link to perform a propterties file conversion.
I'm getting a conversion error when converting our current weblogic.properties file. This properties file is working fine in WL5.1. The web console begins the conversion process ok, but it fails before completion (html err msg below).
I'm trying to determine the cause of this error, but there's very little output reported to the console, except a couple of warnings. Also, I don't see any log files.
I do get what looks like some partial conversion results in my new domain directory in fileRealm.properties. There are recognizable properties from the converted weblogic.properties file in here.
Has anyone encountered/surmounted similiar difficulty? Any debugging tips would be appreciated. TIA.
JohnH
p.s. The output/error message on the html page looks like:
New Domain name is MyDomain-1
Converting Server properties
Converting Server Debug Properties
Converting WebServer properties
Converting WebApp Component Properties
Converting JDBC Specific properties
Converting CORBA IIOP properties
Converting StartupClass properties
Converting Shutdown Class properties
Converting MailSession Properties
Converting FileT3 properties
Converting JMS properties
Converting Security Properties
Converting the PasswordPolicy properties
Converting User Group and ACL properties
Conversion failed

Ya it will be corrected in the next beta refresh.
Jim Clark <[email protected]> wrote in message
news:[email protected]..
Typo in weblogic.properties conversion console page
"Select server weblogic.properies"
and
"Select cluster weblogic.properies"
Both are missing the "t"

Setting the debug level of log

What do you set in order to get more verbose log messages from OC4J? I can't tell if things are going right ..

http://www.orionserver.com/howtos/debug-tips.html
I hope this link will give you some help!

[Solved] Debugging in QtCreator in "c++" & "qml" modes simultaneously

Sorry for my English.
It seems that last upgrade breaks my QtCreator or gdb.
When I try to launch my program under QtCreator in debug mode the program starts but I doesn't see GUI.
"ps aux" tells that program was started.
QtCreator writes next output:
Could not load shared library symbols for linux-gate.so.1. Do you need "set solib-search-path" or "set sysroot".
But this message was also before upgrading and all was fine.
Important note: if debug option is "c++" or "qml" (on Project page) then program starts fine and I can debug,
but if both options are set simultaneously then I can't see GUI of the program and any breakpoint leads to hanging of the debugger.
Help me, I need both debugger options "c++" and "qml" simultaneously!
Last edited by yerdnas (2014-06-06 11:09:08)

I have the same issue. Perhaps we should file a bug report?
Thanks for the disable qml debugging tip, I'll at least be able to get some work done now.

Advice to Debug / Find source of issue?

Hello,
I'm having problem with an ApEx app that is kinda large and complex.
Does anyone have useful suggestions or tips for finding where a program data bug is happening ??
My ApEx version is 3.2.1.00.12
Any debugging / tracing advice is greatly appreciated !
Problem Details ::::::
Somewhere, the values in ApEx collection APEX_APPLICATION.G_F33 is getting set with duplicates.
In a Page Process:
FOR i in 1..APEX_APPLICATION.G_F33.COUNT LOOP
-- This code is running too many times
END LOOP;

In very general terms, here as some debugging tips:
1. (This is a pre-requisite btw - stop what you are doing and do this first): Review the APEX documentation for a guide to debugging. There are references to the "Session Window" and "Debug Mode" - making use of these views can give you a lot of detailed information about the current state of your application and what is happening during the page load.
2. Make use of the wwv_flow.debug function to output messages, which can then be viewed in the"Debug" information (see above) - this is kind of equivalent to the use of the old DBMS_OUTPUT in the PL/SQL world.
3. For more complex application code/logic, attempt to log information using some sort of logging framework - either something custom-built or by using an "off the shelf" solution
I would suggest following option 3, particularly for capturing error/exception information. I used to use my own custom logging package/table combination but I moved over to using Tyler Muth's APEX Logger framework * , which has helped improve the debugging/alpha testing of my applications no end.
It's very easy to install, simply requiring some relatively minor database privileges and the running of a single SQL script (obviously if you don't have the relevant privileges, speak to your local house-trained DBA - bring beer/chocolate/[bribe of choice] to facilitate).
Whilst writing some application code, you can insert calls to the relevant logger function in areas that require observation. These entries can then be queried through built-in views. In addition, you can capture complete Apex session information with a single function call, thus allowing you to review the entire application state at a given moment of execution (particularly helpful for situations where references are made to multiple pages or application items).
Once you've completed your debugging phase, you also have the option of changing the logging levels so that (e.g. when you move to a production environment) you can switch off logging completely or leave it to log errors only.
(*) I have no affiliation with Tyler Muth nor APEX Logger incidentally

Photoshop HTML Panels Tips - tutorial series

Hello,
I've been putting together a series of tips on HTML Panels creation - both from personal experiments and collecting information around. Each tip focuses on a particular topic, it's quite short and provides the code for a demo panel.
You can find the whole series here, so far I've covered:
Tip #1 - Debugging
Tip #2 - Including multiple JSX
Tip #3 - Get data from JSX and send it to HTML
Tip #4 - Passing Objects from HTML to JSX
Tip #5 - Passing Objects from JSX to HTML
Tip #6 - Integrating Topcoat CSS library
Tip #7 - Photoshop Events, Take 1
Tip #8 - Photoshop Events, Take 2
Tip #9 - Panel Persistence (to be published asap)
Tips are about Photoshop panels, but general principles apply to other apps too.
I'll share more as soon as... I have new finding to share!
Best,
Davide Barranca
www.davidebarranca.com

Update (December 5, 2014)
Two new tips, #15 and #16 have been added, enjoy :-)
Recently added/updated Tips in bold - You can find the whole series here, so far the topic list is:
Tip #16 - AngularJS Binding bug patch
Tip #15 - Asynchronous vs. Synchronous
Tip #14 - Flyout Menu
Tip #13 - Automate ZXP Packaging with Gulp.js
Tip #12 - CEP Application Events
Tip #11 - CEP Events (ExternalObject)
Tip #10 - Packaging / ZXP Installers
Tip #9 - Panel Persistence
Tip #8 - Photoshop Events, Take 2
Tip #7 - Photoshop Events, Take 1
Tip #6 - Integrating Topcoat CSS library
Tip #5 - Passing Objects from JSX to HTML
Tip #4 - Passing Objects from HTML to JSX
Tip #3 - Get data from JSX and send it to HTML
Tip #2 - Including multiple JSX
Tip #1 - Debugging

Lightroom -traceback debugging tip

Similar Messages

Maybe you are looking for