Possible CVI13 Debug Mode Bug

I have found a possible bug in Debug mode in CVI13.  The issue is a bit complicated.  It has to do with returning a struct from a function, then referencing a char pointer in that struct in a call to sprintf.  The basic code is:
struct TEST_STRUCT
char *StructString;
} TestStruct =
"Struct String"
struct TEST_STRUCT TestFunction(void)
return TestStruct;
// somewhere in the code...
sprintf(Buff, "%s", TestFunction().StructString);
When executed in Debug mode, the sprintf line generates the runtime warning, "Attempt to read beyond end of string".  If you select Continue the string in Buff is incorrect.  If you run the same program in Release mode it works as expected.  I found this when trying to debug a project previously built in CVI 12.  CVI 12 does not generate this warning.  I also tried refercing the string directly in CVI 13:
sprintf(Buff, "%s", TestStruct.StructString);
 This works correctly.  I also tried using an array in the struct instead of a pointer:
struct TEST_STRUCT
char StructString[50];
} TestStruct =
"Struct String"
This also works correctly.  I also tried using strcpy instead of sprintf:
strcpy(Buff, TestFunction().StructString);
This also works correctly.  The issue appears to be specific to returning a struct and then referecing a char pointer in that struct as a parameter to sprintf.
A sample project is attached.
Tony G
Attachments:
Debug String Problem.zip ‏52 KB

Thanks for pointing this out, I'll go ahead and file a Corrective Action Request on this.
Rob S
Applications Engineer
National Instruments

Similar Messages

  • Nokia N8: Possible Power Saving Mode Bug

    Dear All, 
    For the past week, I've change the way I use my Nokia N8. I decided to set it up in power saving mode during the evening. There is no point for it to be on 3.5G if nobody is using it. Unfortunately, I seem to have hit a problem. At the moment, my N8 is using a pay as you go sim card from O2 and this card is in the phone 24/7. 
    When I activate power saving mode, the phone re-registers with the network and the maximum speed it will have will be EDGE. In the morning, when I take my phone I disable power saving mode and the phone re-registers again with the network. 
    Having said that, on multiple ocassions, my phone showed some worrying symptoms. For example, a few das ago, when I disabled power saving mode, the phone did not show the 3.5G icon and I could not make any phone calls. The coverage was up and down. You might say that, it did not show 3.5G because you had no 3.5G you idiot. That is not true, where I live, there is 3.5G everywhere.
    I was shocked that I could not make any phone calls. After a few reboots and taking SIM card out, I managed to get the phone in working order. 
    Today, the same thing happened. I managed to fix it just a few moments ago. It seems that the power saving mode option has an implementation problem or O2 does not like the way the N8 registers to the network when you enable and disable the said feature.  Has anyone encountered this???

    @m80116, this may well be a solution, but could be problematic if in a weak reception area where only Edge is available ? You could lose data connection completely ! I tend to use Dual mode, and generally don't have an issue, but certainly for anyone living and working in a very strong 3 or 3.5G area it may work very well, wish I had the luxury of being able to use 3G Only 
    If I have helped at all, a click on the White Star is always appreciated :
    you can also help others by marking 'accept as solution' 

  • Is it possible to extract a VI from an executable which has debug mode enabled?

    It is a curiosity question from a client.
    Is it possible to extract a VI from an executable which has debug mode enabled?
    Since the block diagram would not be in edit mode....  Is it possible to "peer" into the executable, look at a VI and recover the block diagram?  This owuld be for a deleted VI that is part of an executable which had debug mode enabled..
    Did anyone try this?
    Curious..

    Extract VIs from an EXE?  No problem.  Even if debugging isn't enabled you can extract VIs, they just won't have block diagrams, and may not have front panels depending on if they were removed in the EXE making process.
    Attached is an example project for making an EXE, the EXE itself, and a VI for extracting VIs from the EXE.  The code is quite primative and it was just meant to demonstrate how this can be done.
    To extract the Main.vi from the Application.exe, run Extract Main.vi from EXE.vi, provide the path to the EXE and the path to where the VI should be saved and then run the VI.  This VI will set keys in the INI file for the application, then run th EXE.  Then it opens an application reference to the EXE, then opens a VI reference to Main.vi.  Then it aborts Main.vi, and extracts it.
    Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
    If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.
    Attachments:
    Test EXE Extract.zip ‏763 KB

  • Disk Mode Bug

    Here's the situation: the "Enable disk use" in the iPod preferences within iTunes is disabled (not checked). I plugged in my nano after putting it in Disk Mode by holding the Center and Play button simultaneously while it's resetting.
    The nano will show up in the Finder for a moment and then it gets unmounted. The nano screen now shows "OK to disconnect" but the nano is still "mounted" within iTunes.
    I believed this is a bug for a)the user has the intention of using the nano's storage space in the Finder by placing it in Disk Mode and the nano's state should take precedence over the iPod preference in iTunes. b)Inconsistency and possible data loss/corruption is also introduced with the nano showing "OK to disconnect" on its screen but iTunes still has ability to interact with the nano.

    I put my iPod in Disk Mode on some occasion when I need to use it for temporary storage or putting notes in the iPod. Since I don't use Disk Mode all the time, I left it off in iTunes preferences and I would use the iPod's state to determine whether I'm in Disk Mode or not.
    The bug I mentioned above seems to be caused by iTunes 5 for my 3G iPod is now exhibiting the same behavior.
    The diagnostic or debug mode for the iPod has different button combinations.

  • JNI_CreateJavaVM in debug mode

    Hi,
    on W2K using JDK1.3.1...
    I tried, from my own executable, to launch a JVM in remote debug mode. My IDE for Java is Idea, so it provides me the arguments to provide to that function :
    -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5000
    the other JVM args are                "-Xms150m","-Xmx150m", and the classpath to my jar (given as -Djava.class.path)
    Note that I load the jvm.dll dynamically (using LoadLibrary()). I don't do any static linking...
    The question is :
    If I don't explicitly load the dt_socket.dll using LoadLibrary()
    the JVM refuses to load, with the following message :
    Transport dt_socket failed to initialize, rc = 509.
    FATAL ERROR in native method: No transports initialized
    if I use shared meme instead of tcp, I have a similar message :
    Transport dt_shmem failed to initialize, rc = 509.
    FATAL ERROR in native method: No transports initialized
    Is there any additional args to provide to the JVM so that I don't have to explicitly load the dlls it requires ?
    My goal is to be the as little dependant as possible from the brand/version/installation/Operating System of the JVM...
    Thanks in advance.
    C.Dore

    Well, as a second view, I don't beleive that the dlls that are missing are statically likned. Because the error message is not a Windows message :
    Transport dt_socket failed to initialize, rc = 509.
    FATAL ERROR in native method: No transports initialized
    Thus, the required dlls should be search relatively to the path of the jvm.dll, or the the path of jdwp.dll
    I consider this as a bug.

  • Is it possible to debug a Job which already executed in the Background.

    Hi Friends,
    My Z program has a bug when run it in Quality System.
    If I run this program in foreground to debug, its giving TIME OUT dump.
    If i try to run it in Background and started DEBUG mode using JDBG.
    Still one of the table fetch gives TIME OUT dump.
    Is there any possibility to DEBUG the already executed job?
    Regards,
    VIJI

    Hi,
    If the job is running go to SM50..
    Select the process:
    In the menu..Program/session -> program -> debugging..
    OR
    Fix the break points.
    2) Create job.
    3) Go SM37
    4) Select the job and write "jdbg" in command line.
    1) Use Transaction SM50. This would give you a view of all the background
    processes running in the server.
    2) Choose your background process from the list and got to
    MENU "Program/Mode"->"Program"->"Debugging".
    Regards,
    Suresh Kumar

  • Problem connecting to Realtime system to download or run in debug mode

    I have updated my LabWindows\CVI to 2013. I have a PXI system with a PXIe-8101 controller. The PXIe-controller has a real-time OS installed. I have been programming this system for a while now so I am not exactly a novice anymore. The first time I tried to install the program to my real-time target I got a message which said "LabWindows/CVI cannot connect to the real-time target." It also said " .... The version of the LabWindows/CVI Run-Time Engine for RT must be compatible with the version of the LabWindows/CVI development environment."
    So I figured that was the problem. My next step was to go into MAX and sure enough was getting all sorts of flags and errors when I used the real-time software Wizard in MAX by right clicking on the Remote software and clicking on Add/Remove Software. And like I suspected there were several flags indicating a software differences. My next step was to update the software in my real-time target to resolve the problem. After I did that I compiled the code and installed it on my remote system.  Everything seemed OK.
    The following Monday I restarted LabWindows/CVI and made a couple of changes and tried to build and install to my real-time target. I get that same message as in the first paragraph. So I thought I might not have real-time system  booted up correctly or something like that so I checked all of that and it looked OK. Next I opened up MAX and it could see my real-time target just fine.
    When I had my LabWindows/CVI 2012 I did not have this problem. I think maybe there is some incompatibliity issues with my LabWindows 2013; has anyone had a similar problem? I am able to get around the problem by building the release version and copying it to the PXI with CuteFTP V9.0 but I cannot do run my program in debug mode with my LabWindows/CVI and if you may have noticed I have other problems which is in another post I put in next week. I am hoping the problems are connected and I can kill two birds with one stone LOL.
    I appreciate any suggestions.
    Thanks,
    Don Pearce

    Hello,
    I want to make sure I'm understanding what you are doing in the LabVIEW project. According to the Getting Started with the LabWindows /CVI Real-Time Module manual, these are the steps to install software on the RT target:
    1. Launch MAX.
    2. Find and expand your RT target under the Remote Systems item in the MAX configuration tree, right-click Software, and select Add/Remove Software. When you select Add/Remove Software, MAX launches the LabVIEW Real-Time Software Wizard. This displays all the National Instruments software and drivers installed on the host computer that you can install on a selected RT target.
    3. Select the software you want to install on the RT target, click the icon next to the software, and select Install the feature.
    You need to install LabWindows/CVI Run-Time Engine for RT to add support for LabWindows/CVI RT applications on the RT target. This component is required for all LabWindows/CVI RT applications.
    The forum post here solved this same issue by installing missing drivers based on this KnowledgeBase article.
    Also, LabWindows/CVI 2013 SP1 has been released. Service Pack 1 (SP1) has many  useful bug fixes (listed here), so I recommend upgrading to LabWindows/CVI 2013 SP1 if possible.
    Taylor B.
    National Instruments

  • JVM crash when using debug mode in eclipse

    Hi,
    I get a SIGSEGV every time I use debug mode in Eclipse. Sometimes after a few breakpoints, sometimes when I start the debug view.
    Have Eclipse helios and JRE 6.0_21-b06 but have also tried 1.6.0_03-b05 with same result.
    The log file (hs_error_pidxxx.log) gives the following:
    # A fatal error has been detected by the Java Runtime Environment:
    # SIGSEGV (0xb) at pc=0xff23259c, pid=2917, tid=2
    # JRE version: 6.0_21-b06
    # Java VM: Java HotSpot(TM) Server VM (17.0-b16 mixed mode solaris-sparc )
    # Problematic frame:
    # C [libc.so.1+0x3259c] strncmp+0x348
    # If you would like to submit a bug report, please visit:
    # http://java.sun.com/webapps/bugreport/crash.jsp
    # The crash happened outside the Java Virtual Machine in native code.
    # See problematic frame for where to report the bug.
    --------------- T H R E A D ---------------
    Current thread (0x0003d800): JavaThread "main" [_thread_in_native, id=2, stack(0xfe300000,0xfe380000)]
    siginfo:si_signo=SIGSEGV: si_errno=0, si_code=1 (SEGV_MAPERR), si_addr=0x00000000
    Registers:
    O0=0x00000001 O1=0x00000000 O2=0x00000001 O3=0x00000000
    O4=0x00000102 O5=0x0125d898 O6=0xfe37d3b8 O7=0xe1dd104c
    G1=0x00105000 G2=0x00007b00 G3=0x00000000 G4=0xe2947b08
    G5=0xfee6e2e8 G6=0x00000000 G7=0xfe3e0200 Y=0x00000000
    PC=0xff23259c nPC=0xff2325a0
    Top of Stack: (sp=0xfe37d3b8)
    0xfe37d3b8: 00000000 e1ebec00 ff2c1bd0 e1ebec00
    0xfe37d3c8: 011966e8 00000001 fee2e000 00001cc4
    0xfe37d3d8: 1d69c014 e2963fec 00000001 00000108
    0xfe37d3e8: 0000006e 0000006e fe37d3f8 e2947bd4
    0xfe37d3f8: e2963ff4 014e2b38 e2963ffc 00000000
    0xfe37d408: fee2e000 011afd80 01da6f38 e2963fec
    0xfe37d418: fe37d484 0125da90 0125dab8 00000002
    0xfe37d428: 00000000 e2974f88 fe37d488 e2350fd4
    Instructions: (pc=0xff23259c)
    0xff23258c: 91 ee 00 00 b4 a6 a0 01 0a bf ff e1 01 00 00 00
    0xff23259c: f8 0e 40 18 fa 0e 40 00 b2 06 60 01 80 a7 00 1d
    Stack: [0xfe300000,0xfe380000], sp=0xfe37d3b8, free space=1f4ff23259ck
    Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
    C [libc.so.1+0x3259c] strncmp+0x348
    C [libpangoft2-1.0.so.0.501.1+0x7bdc]
    C [libswt-pi-gtk-3650.so+0x50fdc] Java_org_eclipse_swt_internal_gtk_OS__1pango_1context_1list_1families+0x74
    j org.eclipse.swt.internal.gtk.OS._pango_context_list_families(I[I[I)V+472954808
    j org.eclipse.swt.internal.gtk.OS._pango_context_list_families(I[I[I)V+0
    j org.eclipse.swt.internal.gtk.OS.pango_context_list_families(I[I[I)V+10
    j org.eclipse.swt.graphics.Device.getFontList(Ljava/lang/String;Z)[Lorg/eclipse/swt/graphics/FontData;+53
    j org.eclipse.jface.resource.FontRegistry.filterData([Lorg/eclipse/swt/graphics/FontData;Lorg/eclipse/swt/widgets/Display;)[Lorg/eclipse/swt/graphics/FontData;+67
    j org.eclipse.jface.resource.FontRegistry.createFont(Ljava/lang/String;[Lorg/eclipse/swt/graphics/FontData;)Lorg/eclipse/jface/resource/FontRegistry$FontRecord;+32
    j org.eclipse.jface.resource.FontRegistry.getFontRecord(Ljava/lang/String;)Lorg/eclipse/jface/resource/FontRegistry$FontRecord;+53
    j org.eclipse.jface.resource.FontRegistry.get(Ljava/lang/String;)Lorg/eclipse/swt/graphics/Font;+2
    j org.eclipse.jface.resource.JFaceResources.getHeaderFont()Lorg/eclipse/swt/graphics/Font;+5
    j org.eclipse.jdt.internal.ui.javaeditor.ClassFileEditor$SourceAttachmentForm.createTitleLabel(Lorg/eclipse/swt/widgets/Composite;Ljava/lang/String;)Lorg/eclipse/swt/widgets/Label;+36
    j org.eclipse.jdt.internal.ui.javaeditor.ClassFileEditor$SourceAttachmentForm.createControl(Lorg/eclipse/swt/widgets/Composite;)Lorg/eclipse/swt/widgets/Control;+99
    j org.eclipse.jdt.internal.ui.javaeditor.ClassFileEditor.verifyInput(Lorg/eclipse/ui/IEditorInput;)V+95
    j org.eclipse.jdt.internal.ui.javaeditor.ClassFileEditor.createPartControl(Lorg/eclipse/swt/widgets/Composite;)V+96
    j org.eclipse.ui.internal.EditorReference.createPartHelper()Lorg/eclipse/ui/IEditorPart;+361
    j org.eclipse.ui.internal.EditorReference.createPart()Lorg/eclipse/ui/IWorkbenchPart;+27
    j org.eclipse.ui.internal.WorkbenchPartReference.getPart(Z)Lorg/eclipse/ui/IWorkbenchPart;+65
    j org.eclipse.ui.internal.EditorReference.getEditor(Z)Lorg/eclipse/ui/IEditorPart;+2
    j org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(Lorg/eclipse/ui/IEditorInput;Ljava/lang/String;ZILorg/eclipse/ui/IMemento;)Lorg/eclipse/ui/IEditorPart;+233
    j org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(Lorg/eclipse/ui/IEditorInput;Ljava/lang/String;ZILorg/eclipse/ui/IMemento;)Lorg/eclipse/ui/IEditorPart;+27
    j org.eclipse.ui.internal.WorkbenchPage.access$11(Lorg/eclipse/ui/internal/WorkbenchPage;Lorg/eclipse/ui/IEditorInput;Ljava/lang/String;ZILorg/eclipse/ui/IMemento;)Lorg/eclipse/ui/IEditorPart;+8
    j org.eclipse.ui.internal.WorkbenchPage$10.run()V+29
    j org.eclipse.swt.custom.BusyIndicator.showWhile(Lorg/eclipse/swt/widgets/Display;Ljava/lang/Runnable;)V+116
    j org.eclipse.ui.internal.WorkbenchPage.openEditor(Lorg/eclipse/ui/IEditorInput;Ljava/lang/String;ZILorg/eclipse/ui/IMemento;)Lorg/eclipse/ui/IEditorPart;+59
    j org.eclipse.ui.internal.WorkbenchPage.openEditor(Lorg/eclipse/ui/IEditorInput;Ljava/lang/String;ZI)Lorg/eclipse/ui/IEditorPart;+7
    j org.eclipse.debug.internal.ui.sourcelookup.SourceLookupFacility$1.run()V+41
    j org.eclipse.swt.custom.BusyIndicator.showWhile(Lorg/eclipse/swt/widgets/Display;Ljava/lang/Runnable;)V+116
    j org.eclipse.debug.internal.ui.sourcelookup.SourceLookupFacility.openEditor(Lorg/eclipse/ui/IWorkbenchPage;Lorg/eclipse/ui/IEditorInput;Ljava/lang/String;)Lorg/eclipse/ui/IEditorPart;+26
    j org.eclipse.debug.internal.ui.sourcelookup.SourceLookupFacility.openEditor(Lorg/eclipse/debug/ui/sourcelookup/ISourceLookupResult;Lorg/eclipse/ui/IWorkbenchPage;)Lorg/eclipse/ui/IEditorPart;+201
    j org.eclipse.debug.internal.ui.sourcelookup.SourceLookupFacility.display(Lorg/eclipse/debug/ui/sourcelookup/ISourceLookupResult;Lorg/eclipse/ui/IWorkbenchPage;)V+3
    j org.eclipse.debug.ui.DebugUITools.displaySource(Lorg/eclipse/debug/ui/sourcelookup/ISourceLookupResult;Lorg/eclipse/ui/IWorkbenchPage;)V+5
    j org.eclipse.debug.internal.ui.elements.adapters.StackFrameSourceDisplayAdapter$SourceDisplayJob.runInUIThread(Lorg/eclipse/core/runtime/IProgressMonitor;)Lorg/eclipse/core/runtime/IStatus;+24
    j org.eclipse.ui.progress.UIJob$1.run()V+53
    J org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Z)Z
    J org.eclipse.swt.widgets.Display.runAsyncMessages(Z)Z
    J org.eclipse.ui.internal.Workbench.runEventLoop(Lorg/eclipse/jface/window/Window$IExceptionHandler;Lorg/eclipse/swt/widgets/Display;)V
    j org.eclipse.ui.internal.Workbench.runUI()I+555
    j org.eclipse.ui.internal.Workbench.access$4(Lorg/eclipse/ui/internal/Workbench;)I+1
    j org.eclipse.ui.internal.Workbench$7.run()V+55
    j org.eclipse.core.databinding.observable.Realm.runWithDefault(Lorg/eclipse/core/databinding/observable/Realm;Ljava/lang/Runnable;)V+12
    j org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Lorg/eclipse/swt/widgets/Display;Lorg/eclipse/ui/application/WorkbenchAdvisor;)I+18
    j org.eclipse.ui.PlatformUI.createAndRunWorkbench(Lorg/eclipse/swt/widgets/Display;Lorg/eclipse/ui/application/WorkbenchAdvisor;)I+2
    j org.eclipse.ui.internal.ide.application.IDEApplication.start(Lorg/eclipse/equinox/app/IApplicationContext;)Ljava/lang/Object;+99
    j org.eclipse.equinox.internal.app.EclipseAppHandle.run(Ljava/lang/Object;)Ljava/lang/Object;+135
    j org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(Ljava/lang/Object;)Ljava/lang/Object;+103
    j org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(Ljava/lang/Object;)Ljava/lang/Object;+29
    j org.eclipse.core.runtime.adaptor.EclipseStarter.run(Ljava/lang/Object;)Ljava/lang/Object;+149
    j org.eclipse.core.runtime.adaptor.EclipseStarter.run([Ljava/lang/String;Ljava/lang/Runnable;)Ljava/lang/Object;+183
    v ~StubRoutines::call_stub
    V [libjvm.so+0x15e33c]
    V [libjvm.so+0x797afc]
    V [libjvm.so+0x217704]
    V [libjvm.so+0x215d8c]
    C [libjava.so+0x10bfc] Java_sun_reflect_NativeMethodAccessorImpl_invoke0+0x18
    j sun.reflect.NativeMethodAccessorImpl.invoke0(Ljava/lang/reflect/Method;Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;+746878888
    j sun.reflect.NativeMethodAccessorImpl.invoke0(Ljava/lang/reflect/Method;Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;+0
    j sun.reflect.NativeMethodAccessorImpl.invoke(Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;+87
    j sun.reflect.DelegatingMethodAccessorImpl.invoke(Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;+6
    j java.lang.reflect.Method.invoke(Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;+161
    j org.eclipse.equinox.launcher.Main.invokeFramework([Ljava/lang/String;[Ljava/net/URL;)V+211
    j org.eclipse.equinox.launcher.Main.basicRun([Ljava/lang/String;)V+126
    j org.eclipse.equinox.launcher.Main.run([Ljava/lang/String;)I+4
    j org.eclipse.equinox.launcher.Main.main([Ljava/lang/String;)V+10
    v ~StubRoutines::call_stub
    V [libjvm.so+0x15e33c]
    V [libjvm.so+0x2012dc]
    C [java+0x3ab8]
    Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
    j org.eclipse.swt.internal.gtk.OS._pango_context_list_families(I[I[I)V+0
    j org.eclipse.swt.internal.gtk.OS.pango_context_list_families(I[I[I)V+10
    j org.eclipse.swt.graphics.Device.getFontList(Ljava/lang/String;Z)[Lorg/eclipse/swt/graphics/FontData;+53
    j org.eclipse.jface.resource.FontRegistry.filterData([Lorg/eclipse/swt/graphics/FontData;Lorg/eclipse/swt/widgets/Display;)[Lorg/eclipse/swt/graphics/FontData;+67
    j org.eclipse.jface.resource.FontRegistry.createFont(Ljava/lang/String;[Lorg/eclipse/swt/graphics/FontData;)Lorg/eclipse/jface/resource/FontRegistry$FontRecord;+32
    j org.eclipse.jface.resource.FontRegistry.getFontRecord(Ljava/lang/String;)Lorg/eclipse/jface/resource/FontRegistry$FontRecord;+53
    j org.eclipse.jface.resource.FontRegistry.get(Ljava/lang/String;)Lorg/eclipse/swt/graphics/Font;+2
    j org.eclipse.jface.resource.JFaceResources.getHeaderFont()Lorg/eclipse/swt/graphics/Font;+5
    j org.eclipse.jdt.internal.ui.javaeditor.ClassFileEditor$SourceAttachmentForm.createTitleLabel(Lorg/eclipse/swt/widgets/Composite;Ljava/lang/String;)Lorg/eclipse/swt/widgets/Label;+36
    j org.eclipse.jdt.internal.ui.javaeditor.ClassFileEditor$SourceAttachmentForm.createControl(Lorg/eclipse/swt/widgets/Composite;)Lorg/eclipse/swt/widgets/Control;+99
    j org.eclipse.jdt.internal.ui.javaeditor.ClassFileEditor.verifyInput(Lorg/eclipse/ui/IEditorInput;)V+95
    j org.eclipse.jdt.internal.ui.javaeditor.ClassFileEditor.createPartControl(Lorg/eclipse/swt/widgets/Composite;)V+96
    j org.eclipse.ui.internal.EditorReference.createPartHelper()Lorg/eclipse/ui/IEditorPart;+361
    j org.eclipse.ui.internal.EditorReference.createPart()Lorg/eclipse/ui/IWorkbenchPart;+27
    j org.eclipse.ui.internal.WorkbenchPartReference.getPart(Z)Lorg/eclipse/ui/IWorkbenchPart;+65
    j org.eclipse.ui.internal.EditorReference.getEditor(Z)Lorg/eclipse/ui/IEditorPart;+2
    j org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(Lorg/eclipse/ui/IEditorInput;Ljava/lang/String;ZILorg/eclipse/ui/IMemento;)Lorg/eclipse/ui/IEditorPart;+233
    j org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(Lorg/eclipse/ui/IEditorInput;Ljava/lang/String;ZILorg/eclipse/ui/IMemento;)Lorg/eclipse/ui/IEditorPart;+27
    j org.eclipse.ui.internal.WorkbenchPage.access$11(Lorg/eclipse/ui/internal/WorkbenchPage;Lorg/eclipse/ui/IEditorInput;Ljava/lang/String;ZILorg/eclipse/ui/IMemento;)Lorg/eclipse/ui/IEditorPart;+8
    j org.eclipse.ui.internal.WorkbenchPage$10.run()V+29
    j org.eclipse.swt.custom.BusyIndicator.showWhile(Lorg/eclipse/swt/widgets/Display;Ljava/lang/Runnable;)V+116
    j org.eclipse.ui.internal.WorkbenchPage.openEditor(Lorg/eclipse/ui/IEditorInput;Ljava/lang/String;ZILorg/eclipse/ui/IMemento;)Lorg/eclipse/ui/IEditorPart;+59
    j org.eclipse.ui.internal.WorkbenchPage.openEditor(Lorg/eclipse/ui/IEditorInput;Ljava/lang/String;ZI)Lorg/eclipse/ui/IEditorPart;+7
    j org.eclipse.debug.internal.ui.sourcelookup.SourceLookupFacility$1.run()V+41
    j org.eclipse.swt.custom.BusyIndicator.showWhile(Lorg/eclipse/swt/widgets/Display;Ljava/lang/Runnable;)V+116
    j org.eclipse.debug.internal.ui.sourcelookup.SourceLookupFacility.openEditor(Lorg/eclipse/ui/IWorkbenchPage;Lorg/eclipse/ui/IEditorInput;Ljava/lang/String;)Lorg/eclipse/ui/IEditorPart;+26
    j org.eclipse.debug.internal.ui.sourcelookup.SourceLookupFacility.openEditor(Lorg/eclipse/debug/ui/sourcelookup/ISourceLookupResult;Lorg/eclipse/ui/IWorkbenchPage;)Lorg/eclipse/ui/IEditorPart;+201
    j org.eclipse.debug.internal.ui.sourcelookup.SourceLookupFacility.display(Lorg/eclipse/debug/ui/sourcelookup/ISourceLookupResult;Lorg/eclipse/ui/IWorkbenchPage;)V+3
    j org.eclipse.debug.ui.DebugUITools.displaySource(Lorg/eclipse/debug/ui/sourcelookup/ISourceLookupResult;Lorg/eclipse/ui/IWorkbenchPage;)V+5
    j org.eclipse.debug.internal.ui.elements.adapters.StackFrameSourceDisplayAdapter$SourceDisplayJob.runInUIThread(Lorg/eclipse/core/runtime/IProgressMonitor;)Lorg/eclipse/core/runtime/IStatus;+24
    j org.eclipse.ui.progress.UIJob$1.run()V+53
    J org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Z)Z
    J org.eclipse.swt.widgets.Display.runAsyncMessages(Z)Z
    J org.eclipse.ui.internal.Workbench.runEventLoop(Lorg/eclipse/jface/window/Window$IExceptionHandler;Lorg/eclipse/swt/widgets/Display;)V
    j org.eclipse.ui.internal.Workbench.runUI()I+555
    j org.eclipse.ui.internal.Workbench.access$4(Lorg/eclipse/ui/internal/Workbench;)I+1
    j org.eclipse.ui.internal.Workbench$7.run()V+55
    j org.eclipse.core.databinding.observable.Realm.runWithDefault(Lorg/eclipse/core/databinding/observable/Realm;Ljava/lang/Runnable;)V+12
    j org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Lorg/eclipse/swt/widgets/Display;Lorg/eclipse/ui/application/WorkbenchAdvisor;)I+18
    j org.eclipse.ui.PlatformUI.createAndRunWorkbench(Lorg/eclipse/swt/widgets/Display;Lorg/eclipse/ui/application/WorkbenchAdvisor;)I+2
    j org.eclipse.ui.internal.ide.application.IDEApplication.start(Lorg/eclipse/equinox/app/IApplicationContext;)Ljava/lang/Object;+99
    j org.eclipse.equinox.internal.app.EclipseAppHandle.run(Ljava/lang/Object;)Ljava/lang/Object;+135
    j org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(Ljava/lang/Object;)Ljava/lang/Object;+103
    j org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(Ljava/lang/Object;)Ljava/lang/Object;+29
    j org.eclipse.core.runtime.adaptor.EclipseStarter.run(Ljava/lang/Object;)Ljava/lang/Object;+149
    j org.eclipse.core.runtime.adaptor.EclipseStarter.run([Ljava/lang/String;Ljava/lang/Runnable;)Ljava/lang/Object;+183
    v ~StubRoutines::call_stub
    j sun.reflect.NativeMethodAccessorImpl.invoke0(Ljava/lang/reflect/Method;Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;+0
    j sun.reflect.NativeMethodAccessorImpl.invoke(Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;+87
    j sun.reflect.DelegatingMethodAccessorImpl.invoke(Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;+6
    j java.lang.reflect.Method.invoke(Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;+161
    j org.eclipse.equinox.launcher.Main.invokeFramework([Ljava/lang/String;[Ljava/net/URL;)V+211
    j org.eclipse.equinox.launcher.Main.basicRun([Ljava/lang/String;)V+126
    j org.eclipse.equinox.launcher.Main.run([Ljava/lang/String;)I+4
    j org.eclipse.equinox.launcher.Main.main([Ljava/lang/String;)V+10
    v ~StubRoutines::call_stub
    --------------- P R O C E S S ---------------
    Java Threads: ( => current thread )
    0x016fec00 JavaThread "org.eclipse.jdt.internal.ui.text.JavaReconciler" daemon [_thread_blocked, id=300, stack(0xd8f00000,0xd8f80000)]
    0x01a5dc00 JavaThread "org.eclipse.jdt.debug: JDI Event Dispatcher" daemon [_thread_blocked, id=292, stack(0xd9000000,0xd9080000)]
    0x00a3bc00 JavaThread "Timer-2" daemon [_thread_blocked, id=291, stack(0xd9700000,0xd9780000)]
    0x00a41000 JavaThread "Packet Send Manager" daemon [_thread_blocked, id=290, stack(0xd9100000,0xd9180000)]
    0x01f73c00 JavaThread "Packet Receive Manager" daemon [_thread_in_native, id=289, stack(0xd9200000,0xd9280000)]
    0x00e2a400 JavaThread "Timer-1" daemon [_thread_blocked, id=287, stack(0xd9a00000,0xd9a80000)]
    0x0094c000 JavaThread "ServerConnection" [_thread_in_native, id=285, stack(0xd9800000,0xd9880000)]
    0x0094bc00 JavaThread "Process monitor" daemon [_thread_blocked, id=284, stack(0xd9300000,0xd9380000)]
    0x00895c00 JavaThread "Input Stream Monitor" daemon [_thread_blocked, id=283, stack(0xd9400000,0xd9480000)]
    0x01fef800 JavaThread "Output Stream Monitor" daemon [_thread_in_native, id=282, stack(0xd9600000,0xd9680000)]
    0x00a8b000 JavaThread "Output Stream Monitor" daemon [_thread_in_native, id=281, stack(0xd9900000,0xd9980000)]
    0x011dbc00 JavaThread "process reaper" daemon [_thread_in_native, id=280, stack(0xd9500000,0xd9580000)]
    0x01059800 JavaThread "Worker-24" [_thread_blocked, id=261, stack(0xd9c80000,0xd9d00000)]
    0x01059000 JavaThread "Worker-23" [_thread_blocked, id=260, stack(0xde580000,0xde600000)]
    0x02176000 JavaThread "Worker-22" [_thread_blocked, id=248, stack(0xddd00000,0xddd80000)]
    0x01ff0800 JavaThread "Worker-21" [_thread_blocked, id=247, stack(0xda280000,0xda300000)]
    0x00c41c00 JavaThread "Worker-20" [_thread_blocked, id=245, stack(0xdd700000,0xdd780000)]
    0x0268bc00 JavaThread "Worker-19" [_thread_blocked, id=243, stack(0xde000000,0xde080000)]
    0x0141e800 JavaThread "Worker-18" [_thread_blocked, id=242, stack(0xdda00000,0xdda80000)]
    0x019aec00 JavaThread "Worker-16" [_thread_blocked, id=227, stack(0xddf00000,0xddf80000)]
    0x0143b800 JavaThread "org.eclipse.jdt.internal.ui.text.JavaReconciler" daemon [_thread_blocked, id=223, stack(0xddb00000,0xddb80000)]
    0x01022800 JavaThread "org.eclipse.jdt.internal.ui.text.JavaReconciler" daemon [_thread_blocked, id=219, stack(0xdde00000,0xdde80000)]
    0x00a58800 JavaThread "Worker-12" [_thread_blocked, id=211, stack(0xde680000,0xde700000)]
    0x018c5400 JavaThread "pool-1-thread-5" [_thread_blocked, id=187, stack(0xd9d80000,0xd9e00000)]
    0x013cdc00 JavaThread "pool-1-thread-4" [_thread_blocked, id=186, stack(0xda380000,0xda400000)]
    0x002a4c00 JavaThread "pool-1-thread-3" [_thread_blocked, id=185, stack(0xddc00000,0xddc80000)]
    0x0282b400 JavaThread "pool-1-thread-2" [_thread_blocked, id=184, stack(0xd9e80000,0xd9f00000)]
    0x018c6400 JavaThread "pool-1-thread-1" [_thread_blocked, id=183, stack(0xd9f80000,0xda000000)]
    0x00973000 JavaThread "Timer-0" daemon [_thread_blocked, id=75, stack(0xdd800000,0xdd880000)]
    0x00ab8000 JavaThread "Thread-39" daemon [_thread_blocked, id=74, stack(0xdd500000,0xdd580000)]
    0x00dc1400 JavaThread "Worker-6" [_thread_blocked, id=73, stack(0xdd900000,0xdd980000)]
    0x004db000 JavaThread "Thread-32" daemon [_thread_in_native, id=66, stack(0xda4d0000,0xda4e0000)]
    0x011eb000 JavaThread "[ThreadPool Manager] - Idle Thread" daemon [_thread_blocked, id=43, stack(0xdd400000,0xdd480000)]
    0x003e6400 JavaThread "Bundle File Closer" daemon [_thread_blocked, id=27, stack(0xde100000,0xde180000)]
    0x007c6c00 JavaThread "org.eclipse.jdt.internal.ui.text.JavaReconciler" daemon [_thread_blocked, id=26, stack(0xde200000,0xde280000)]
    0x001ce800 JavaThread "Java indexing" daemon [_thread_blocked, id=24, stack(0xde380000,0xde400000)]
    0x00191400 JavaThread "Worker-0" [_thread_blocked, id=21, stack(0xe2580000,0xe2600000)]
    0x01235400 JavaThread "Worker-JM" [_thread_blocked, id=20, stack(0xe2380000,0xe2400000)]
    0x007ff400 JavaThread "[Timer] - Main Queue Handler" daemon [_thread_blocked, id=19, stack(0xe2480000,0xe2500000)]
    0x0074e000 JavaThread "Framework Event Dispatcher" daemon [_thread_blocked, id=17, stack(0xe2680000,0xe2700000)]
    0x00390000 JavaThread "Start Level Event Dispatcher" daemon [_thread_blocked, id=16, stack(0xe2780000,0xe2800000)]
    0x005c9800 JavaThread "State Data Manager" daemon [_thread_blocked, id=15, stack(0xe2880000,0xe2900000)]
    0x00124800 JavaThread "Low Memory Detector" daemon [_thread_blocked, id=13, stack(0xe2a80000,0xe2b00000)]
    0x00122400 JavaThread "CompilerThread1" daemon [_thread_blocked, id=12, stack(0xe2b80000,0xe2c00000)]
    0x00110c00 JavaThread "CompilerThread0" daemon [_thread_blocked, id=11, stack(0xe2c80000,0xe2d00000)]
    0x00118000 JavaThread "Signal Dispatcher" daemon [_thread_blocked, id=10, stack(0xe2d80000,0xe2e00000)]
    0x00107c00 JavaThread "Finalizer" daemon [_thread_blocked, id=9, stack(0xe2e80000,0xe2f00000)]
    0x00106400 JavaThread "Reference Handler" daemon [_thread_blocked, id=8, stack(0xe2f80000,0xe3000000)]
    =>0x0003d800 JavaThread "main" [_thread_in_native, id=2, stack(0xfe300000,0xfe380000)]
    Other Threads:
    0x00103c00 VMThread [stack: 0xe3080000,0xe3100000] [id=7]
    0x0012ec00 WatcherThread [stack: 0xe2980000,0xe2a00000] [id=14]
    VM state:not at safepoint (normal execution)
    VM Mutex/Monitor currently owned by a thread: None
    Heap
    PSYoungGen total 40704K, used 18973K [0xf6000000, 0xf9400000, 0xfb800000)
    eden space 29568K, 59% used [0xf6000000,0xf714b120,0xf7ce0000)
    from space 11136K, 11% used [0xf7e40000,0xf7f7c5c8,0xf8920000)
    to space 10432K, 0% used [0xf89d0000,0xf89d0000,0xf9400000)
    PSOldGen total 90112K, used 71968K [0xeb400000, 0xf0c00000, 0xf6000000)
    object space 90112K, 79% used [0xeb400000,0xefa48298,0xf0c00000)
    PSPermGen total 73728K, used 71408K [0xe3400000, 0xe7c00000, 0xeb400000)
    object space 73728K, 96% used [0xe3400000,0xe79bc298,0xe7c00000)
    Dynamic libraries:
    0x00010000      /proj/atelteadm/tools/jdk1.6.0_21/bin/java
    0xff3a0000      /lib/libthread.so.1
    0xff370000      /proj/atelteadm/tools/jdk1.6.0_21/bin/../jre/lib/sparc/jli/libjli.so
    0xff350000      /lib/libdl.so.1
    0xff200000      /lib/libc.so.1
    0xff390000      /platform/SUNW,Sun-Fire-V445/lib/libc_psr.so.1
    0xfe400000      /proj/atelteadm/tools/jdk1.6.0_21/jre/lib/sparc/server/libjvm.so
    0xff1d0000      /lib/libsocket.so.1
    0xff1f0000      /usr/lib/libsched.so.1
    0xff1b0000      /lib/libm.so.1
    0xff180000      /usr/lib/libCrun.so.1
    0xff160000      /lib/libdoor.so.1
    0xff080000      /lib/libnsl.so.1
    0xfef80000      /lib/libm.so.2
    0xff050000      /lib/libscf.so.1
    0xff140000      /lib/libuutil.so.1
    VM Arguments:
    jvm_args: -Xms128m -Xmx256m -XX:MaxPermSize=128m
    java_command: /proj/atelteadm/tools/eclipse_dist_jcat/e4e_fix//plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar -os solaris -ws gtk -arch sparc -showsplash -launcher /proj/atelteadm/tools/eclipse_dist_jcat/e4e_fix/eclipse -name Eclipse --launcher.library /proj/atelteadm/tools/eclipse_dist_jcat/e4e_fix//plugins/org.eclipse.equinox.launcher.gtk.solaris.sparc_1.1.0.v20100503/eclipse_1307.so -startup /proj/atelteadm/tools/eclipse_dist_jcat/e4e_fix//plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar -exitdata 74000027 -install /proj/atelteadm/tools/eclipse_dist_jcat/e4e_fix -nl en_US -showlocation -vm /proj/atelteadm/tools/jdk1.6.0_21//bin/java -vmargs -Xms128m -Xmx256m -XX:MaxPermSize=128m -jar /proj/atelteadm/tools/eclipse_dist_jcat/e4e_fix//plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar
    Launcher Type: SUN_STANDARD
    Environment Variables:
    PATH=/usr/local/opt/apssystem/aps_9.1/bin:/proj/aps/bin:/home/ehollis/.afs/0/rbin:/home/ehollis/.afs/0/pbin:/env/seli/bin:/home/ehollis/.afs/0/ibin:/usr/atria/bin:/usr/afsws/bin:/usr/bin:/usr/X/bin:/usr/dt/bin:/usr/openwin/demo:/usr/openwin/bin:/usr/dt/bin:/usr/ccs/bin:/usr/sbin:/sbin:/usr/ucb:/opt/seli/bin:/opt/sge/seli/etegrid/bin:/opt/sge/seli/bctgrid/bin:/usr/ucb:.
    LD_LIBRARY_PATH=/proj/atelteadm/tools/jdk1.6.0_21/jre/lib/sparc/server:/proj/atelteadm/tools/jdk1.6.0_21/jre/lib/sparc:/proj/atelteadm/tools/jdk1.6.0_21/jre/../lib/sparc:/app/gtk+/2.2.2/lib:/usr/sfw/lib/mozilla/
    SHELL=/bin/tcsh
    DISPLAY=:16.0
    HOSTTYPE=sun4
    OSTYPE=solaris
    MACHTYPE=sparc
    Signal Handlers:
    SIGSEGV: [libjvm.so+0x87b320], sa_mask[0]=0xffbffeff, sa_flags=0x0000000c
    SIGBUS: [libjvm.so+0x87b320], sa_mask[0]=0xffbffeff, sa_flags=0x0000000c
    SIGFPE: [libjvm.so+0x1c4174], sa_mask[0]=0xffbffeff, sa_flags=0x0000000c
    SIGPIPE: SIG_IGN, sa_mask[0]=0x00000000, sa_flags=0x00000000
    SIGXFSZ: [libjvm.so+0x1c4174], sa_mask[0]=0xffbffeff, sa_flags=0x0000000c
    SIGILL: [libjvm.so+0x1c4174], sa_mask[0]=0xffbffeff, sa_flags=0x0000000c
    SIGUSR1: SIG_DFL, sa_mask[0]=0x00000000, sa_flags=0x00000000
    SIGUSR2: SIG_DFL, sa_mask[0]=0x00000000, sa_flags=0x00000000
    SIGQUIT: [libjvm.so+0x7560bc], sa_mask[0]=0xffbffeff, sa_flags=0x00000004
    SIGHUP: [libjvm.so+0x7560bc], sa_mask[0]=0xffbffeff, sa_flags=0x00000004
    SIGINT: [libjvm.so+0x7560bc], sa_mask[0]=0xffbffeff, sa_flags=0x00000004
    SIGTERM: [libjvm.so+0x7560bc], sa_mask[0]=0xffbffeff, sa_flags=0x00000004
    SIG39: [libjvm.so+0x759ae8], sa_mask[0]=0x00000000, sa_flags=0x00000008
    SIG40: [libjvm.so+0x1c4174], sa_mask[0]=0xffbffeff, sa_flags=0x0000000c
    --------------- S Y S T E M ---------------
    OS: Solaris 10 10/08 s10s_u6wos_07b SPARC
    uname:SunOS 5.10 Generic_142900-13 sun4u (T2 libthread)
    vm_info: Java HotSpot(TM) Server VM (17.0-b16) for solaris-sparc JRE (1.6.0_21-b06), built on Jun 22 2010 01:34:33 by "" with Workshop 5.8
    Any clues anyone?

    get a SIGSEGV every time I use debug mode in EclipseSo if you create a hello world program and then debug it, it crashes?
    If yes then the causes would be
    1. The VM(s) binaries are corrupted. Plural as it depends on how you run Eclipse.
    2. Something else installed on your system at the OS level (or at least always running) is corrupt or is corrupting the OS.
    3. A hardware failure.

  • Flash Builder Design Mode Bug Workaround (!!!)

    I've been fighting this annoyance since FB4 came out, and while I still don't think that custom/embedded fonts in design view are fixed by this, I've been able to reproduce this "fix" (workaround) to get design view to show fonts/theme correctly under some very specific circumstances on two separate PCs.
    If anyone from Adobe sees this I'd like to know whether this sounds familiar or is possibly logged as a bug already somewhere in JIRA.. if not I could probably do that as long as it won't be a wasted effort.
    The problem:
    You're using a Halo theme but certain CSS settings (specifically and possibly limited to FONTS) don't work properly in design view even though they work fine in Flash.  Essentially this makes design view practically useless since choice of font family, size, and weight can effect component sizing if you aren't hard-coding component sizes (ugh)... ruining your efforts to use design view for UI design if your UI has any level of complexity (or uses absolute positioning at all).
    The specific circumstances seem to be:
    You're using the Halo theme (you have no special 'skinning' requirements and want Halo defaults w/only CSS customizations)
    You've upgraded a Flex 3 project to Flex 4 SDK (not sure if this is needed to reproduce the issue)
    Using a regular non-embedded font (embedded fonts still do crap out, but even this 'workaround' doesn't fix that problem)
    You're using swc library files such as the Swiz lib, Mate, Flexlib, etc. (I think it's ANY swc, not specific to any one)
    This may also only apply when using an "mx only" project (no Spark), since we're using Halo here
    The two part fix (as far as I can tell you need BOTH before design view works correctly):
    In .actionScriptProperties, add the following bolded line after the compiler tag like so:
      </compiler>
      <theme themeIsDefault="false" themeIsSDK="true" themeLocation="${SDK_THEMES_DIR}/frameworks/themes/Halo"/>
      <applications>
      (I think this may only apply to 'upgraded' projects, as the line does seem to be present in newly created FB4 Halo projects.  My guess is that an "upgraded" project should have such a line added, but doesn't get it due to an oversight/bug.)
    The somewhat painful, and definitely odd part.  Remove all your SWC library files from /libs.  Grab the source code for the libraries and drop them into your project's /src folder as if you'd written them yourself.  (This may require some research and knowledge on special requirements to build the libs, such as with Swiz's compiler metadata compiler settings which you need to put into your project's settings.)  After you get things set up right and the project compiles again, doing a refresh of design view should finally give you proper looking Halo controls and fonts so they look identical to the Flash runtime view.
    Why this works, I've no idea.  I suspect it has something to do with that stupid and annoying (and supposedly 'harmless') design mode warning message you get when you include a library like Swiz or Mate in your project.  (Design mode could not load xxxxxxxxxxxxx.swc. It may be incompatible with this SDK, or invalid. (DesignAssetLoader.CompleteTimeout)) - this warning doesn't break your application, people seem to think it's just a harmless warning..but is it breaking design view?
    If anyone has any idea what's going on here, why this 'fixes' the problem (a better work around), or has any other insight I'd love to hear it.  The combo of needing to do two things (in my specific case) to fix the problem really made this a ROYAL PAIN, I still can't believe I found it.

    Hi Fernando, sorry for the delayed response.  CSS Design Mode is not available for Flex 4 projects, but it is still available in Flex 3 projects.  The reason for this is that designing components in Flex 4 is often a lot different, since it relies highly on the new spark skinning architecture.  There is, however, an Appearance panel available in design view which supplies a set of the main inheriting styles. Setting these styles in the Appearance panel will result in assigning values to a global style selector.
    I hope this helps,
    Rob

  • ABAP Runtime error in debug mode

    Hi all,
    I am facing foll. run time error in debug mode
    Runtime Error          DBIF_RSQL_INVALID_CURSOR
    Except.                CX_SY_OPEN_SQL_DB
    Possible causes in the application program:                       
    Within a loop (SELECT/LOOP/EXEC SQL), one of the following        
    statements is used:                                               
    - MESSAGE (apart from MESSAGE S...)                               
    - COMMIT WORK                                                     
    - ROLLBACK WORK                                                   
    - CALL SCREEN                                                     
    - CALL DIALOG                                                     
    - CALL TRANSACTION                                                
    - SUBMIT                                                          
    - BREAK-POINT                                                     
    - WAIT                                                            
    In debugging mode, a program sometimes triggers                   
    a "COMMIT WORK" during the database selection. As a result        
    this termination may also occur in debugging mode with a correct  
    program.                                                          
    A "COMMIT WORK" during debugging may be due to the following reason
    1. A program or screen was regenerated                            
       and updated in the database.                                   
    2. Each user needs a private process in debugging mode, but       
       the number of available processes is restricted. If this       
       limit is exceeded, each debugging step then requires a         
       "COMMIT WORK".       
    its urgent.
    if i run the prg directly to tcode der is not ne error.
    but i want to execute the prg. in the debug mode.
    its a ZPRG.
    with regards,
    Purva.

    hi,
    You need to change your logic.
    Then , i hope your problem wil be solved.
    Because of nested select statements, you are getting that error.
    Declare seperate Internal tables for VBRK,VBRP, KNA!,j_1iexchdr, j_1imtchid.
    Declare Itab_final with all required fields from all tables.
    Dont use select-endselect anywhere.
    I am giving Pseudo code here.
    Try to use this logic.
    I used question mark in code : there you need to use ur required field names.
    Hope it wil help you.
    select vbeln kunrg zterm bukrs knumv netwr kunrg from vbrk into corresponding fields of table itab1
    where vbeln = docno.
    select matnr posnr arktx fkimg meins netwr werks aubel from vbrp into corresponding fields of table itab2 for all entries in itab1
    where vbeln = itab-vbeln.
    select name1 stras pstlz ort01 land1 from kna1 into corresponding fields of table itab3 for all entries in itab1
    where kunnr = itab1-kunrg.
    select preprn exdat docno from j_1iexchdr into corresponding fields of  table itab4  for all entries in itab1
    where rdoc = itab1-vbeln.
    select j_1ichid from j_1imtchid into corresponding fields of table itab5 for all entries in itab2
    where matnr = itab2-matnr.
    Loop at itab1 into wa_itab1.
    read table itab2 into wa_itab2 index sy-tabix.
    read table itab3 into wa_itab2 index sy-tabix.
    read table itab4 into wa_itab2 index sy-tabix.
    read table itab5 into wa_itab2 index sy-tabix.
    itab_final = itab1-?
    itab_final = itab1-?
    itab_final = itab2-?
    itab_final = itab3-?
    itab_final = itab4-?
    itab_final = itab5-?
    append itab.
    endloop.
    select eikto from knb1 into table wa_knb1
    where kunnr = itab_fianl-kunrg
    and bukrs = itab-bukrs.
    select kawrt kbetr kwert kschl kposn knumv from konv into corresponding fields of wa_konv
    where knumv = itab_fianl-knumv
    and kposn = itab_final-posnr.
    append wa_konv.
    endselect.
    Regards
    Sandeep Reddy

  • Garble code in debug mode

    hi,
    i downloaded a txt file from 3rd party software and upload to sap. all country are ok except 1 country.
    in 1 of the line, there is a character at the begining of the line :
    &#38168;?20:070511
    it should actually be :20:070511.
    this character only can be seen in debug mode. i tried to delete the line and type in manually in the txt file and reupload to sap but the character still there.
    what could be the cause and how to do away with it?
    thanks

    Hi,
    If possible, please use GUI_UPLOAD, if its available on your system.
    CODE PAGE helps identify SAP, which Texts/characters its dealing with.
    Each country has different code page.
    Chinense say 1100
    Best regards,
    Prashant

  • Extraction in debug mode without RSA3

    Hi,
    does anyone know, if there is a way to run an extraction in debug mode on the R/3 side without using RSA3 or RSA7? It has to be a real delta extraction triggered by an InfoPackage in BW.
    I've also tried the "simulate update" function in the monitor (right-click on Data Package), but that only simulates/ debugs the BW-BW transfer.
    Thanks in advance!
    Gerrit

    Hi Gerrit,
    Your requirement is only feasible if your extarctor is based on a function module. In such a case you can set a breakpoint in the function module and when you execute the infopackage the debugger will halt at the breakpoint.
    I dont think it is possible for datasource based on table/view.
    Bye
    Dinesh

  • Problem viewing cursor value in debug mode

    Hi eveybody!
    I'm French and new here.
    I know some topics deal with my subject but I don't really understand.
    Here's my environnement :
    Win2000 / ORA 9iR2 / SQL DEVELOPPER 1.0.0.15.57
    As some people say when i'm in debug mode (after compiling my procedure PL/SQL for debug) I can't see any value of my cursors !
    Ex :
    CURSOR cur IS
    SELECT COL1, COL2
    FROM TABLE1;
    v_cur cur%ROWTYPE;
    For v_cur in cur
    Loop
    If v_cur.COL1 = 'toto' then
    'do something' ;
    End if;
    End Loop;
    When I run this step by step in debug mode I can't see the data of my cursor in the data or smartdata pane.
    The values of my cursor is allways null !
    I guess I'm not the only one to see that bug.
    My question is should I wait a new release of sql developer or is there any solution for this problem?
    Anyway I want to congratulate the developers team who create this tool which is fabulous! It makes me forget TOAD and it's totally free.
    Thanks a lot for this job.
    Greg

    Here is a piece of code I use:
    CREATE OR REPLACE PROCEDURE sm_list AS CURSOR emp_cursor IS
    SELECT d.department_name,
    e.last_name
    FROM departments d,
    employees e
    WHERE d.department_id = e.department_id;
    emp_record emp_cursor % rowtype;
    BEGIN
    FOR emp_record IN emp_cursor
    LOOP
    DBMS_OUTPUT.PUT_LINE(emp_record.last_name);
    END LOOP;
    END;
    With this example, I agree, the smart data is null. Logged a bug. However, note that I do see values in the data tab and can modify and watch these values.
    When using cursors I've been looping and then fetching into cursor records, i.e.:
    FETCH emp_cursor
    INTO emp_record;
    emp_tab(i) := emp_record;
    and then the values display in the Smart data and data tabs.
    Sue

  • Deserialization works only in debug mode

    When I try to deserialize an XML document (defined via File-Connection) it works fine in debug mode but I get an error in non-debug-mode. What's the problem here?
    Error: 2011-12-29 19:31:40.25
    Code: 0x00000001
    Source: Read data from SAP
    Description: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.InvalidOperationException: There is an error in X
    ML document (0, 0). ---> System.TypeInitializationException: The type initializer for 'Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderList1' threw an exception
    . ---> System.NullReferenceException: Object reference not set to an instance of an object.
    at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderList1..cctor()
    --- End of inner exception stack trace ---
    at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderList1..ctor()
    at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializerContract.get_Reader()
    at System.Xml.Serialization.TempAssembly.InvokeReader(XmlMapping mapping, XmlReader xmlReader, XmlDeserializationEvents events, String encodingStyle)
    at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
    --- End of inner exception stack trace ---
    at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
    at System.Xml.Serialization.XmlSerializer.Deserialize(TextReader textReader)

    Yes, there is a potential for a bug. Thus, feel free to log it in
    MS Connect.
    You need to deploy it to the GAC, too. I will better point you to a blog post that covers this: http://www.hoekstra.co.uk/index.php/software-mainmenu-36/ssis-mainmenu-75/73-create-and-use-a-c-assembly-for-ssis.html?start=1
    I suggest when you go live you create a script that will take care of all, but it is not too too laborious.
    Arthur My Blog
    Are you 100% sure? Because I can see that SSIS seeks for the dll in ...DTS/binn. So I see no need to pollute the GAC with this dll.
    My dll is not deployed into the GAC and when I remove it, it will no longer work. I think it works in DTS/binn because the DTExec.exe is located there?
    LOG: This bind starts in default load context.
    LOG: Using application configuration file: c:\Program Files\Microsoft SQL Server\100\DTS\binn\DTExec.exe.Config
    LOG: Using machine configuration file from c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\config\machine.config.
    LOG: Policy not being applied to reference at this time (private, custom, partial, or location-based assembly bind).
    LOG: Attempting download of new URL file:///c:/Program Files/Microsoft SQL Server/100/DTS/binn/ClassLibrary1.DLL.
    LOG: Attempting download of new URL file:///c:/Program Files/Microsoft SQL Server/100/DTS/binn/ClassLibrary1/ClassLibrary1.DLL.
    LOG: Attempting download of new URL file:///c:/Program Files/Microsoft SQL Server/100/DTS/binn/ClassLibrary1.EXE.
    LOG: Attempting download of new URL file:///c:/Program Files/Microsoft SQL Server/100/DTS/binn/ClassLibrary1/ClassLibrary1.EXE.

  • Debug mode (EP6 SP 2) crashs from time to time

    hi folks,
    we got a very well running portal ep6 sp2 which
    we use for iview development. the developers use
    pdk and eclipse and we start the portal in debug
    mode.
    what happens is that from time to time it gets
    unpossible to connect to the debug port. it is not
    possbible to debug an iview from eclipse. the
    connection to the debug port is not possible anymore.
    the only solutions i got is a portal restart to ensure
    that our developer can use the debug port. but that
    takes too much time. does anybody know what leads to that
    phenomenon? and how can we reanimate the portal to be
    debugged without a complete restart?
    i really appreciate any help,
    maik

    Hi Tracy,
    Has it ever been shut off from AC power for any length of time?
    I'm thinking a dead or weak PRAM Battery may cause the boot mode to change.
    Unless of course it might be a sticky Shift key.
       1. Access the command line by either opening Terminal remotely, or by logging into the computer from another via SSH.
       2. Execute the following command in Terminal or on the command line:
          sudo nvram boot-args="-x"
          (If you want to start in Verbose mode as well, use sudo nvram boot-args="-x -v" instead )
       3. After using Safe Boot, to return to a normal startup, execute this command in Terminal or the command line:
          sudo nvram boot-args=""

Maybe you are looking for