JNI calls using dll build in DEBUG mode

I have deployed a filter which loads a dll in the init method. The dll is build in DEBUG mode. The doFilter() method is never called. But If I build the same dll with out DEBUG parameter the doFilter() method is called. what is the issue? I need to debug the dll by attaching it to Visual Studio.
--JArchie

> i had a requirement to invoke a RFC Async and recieve
> the results in my program ...
That is not possible. When you call an RFC async, you cannot receive the result of the RFC. If you want the results, you have to call the RFC syncronously.
When you debug, the debugger calls the RFC synchronously, to enable you the debugging of the RFC.
Regards
Stefan

Similar Messages

How to give call to dll in indesign plugin

Hello All ,
I am developing one indesign plugin on Mac OS X 10.4.
I want to give a call to one dll in pluging code.
But the problem with mac os x according to my knowladge ,dll need to be build in same project where we are calling that dll.
That is why I build a xyz.dylib in same project for indesign plugin as one of the target. and I am coping it in Indesignplugin package content that is with release mode build.but dll gets build in debug mode.On Mac OS X I am using dlopen and dlsym call . But I am not able to call a dll present in indesign plugin package content. Any idea How to call a dll in indesign plugin on Mac OS X.Should we need tyo build a xyz.dylib file in release mode ?
Thanks,
Pallavi.

Seems to me I don't understand something, or text format plugin isn't quite well example. But, I got some code from sdk to create layer with automation like this:
SPErr MakeLayer(void) {
PIActionDescriptor descriptor = NULL;
PIActionReference reference = NULL;
PIActionDescriptor result = NULL;
SPErr error = kSPNoError;
error = sPSActionDescriptor->Make(&descriptor);
if (error)
goto returnError;
// Move this to the top of the routine!
error = sPSActionReference->Make(&reference);
if (error)
goto returnError;
error = sPSActionReference->PutClass(reference, classLayer);
if (error)
goto returnError;
error = sPSActionDescriptor->PutReference(descriptor, keyNull, reference);
if (error)
goto returnError;
error = sPSActionControl->Play(&result, eventMake, descriptor,
plugInDialogSilent);
if (error)
goto returnError;
returnError:
if (result != NULL) sPSActionDescriptor->Free(result);
if (descriptor != NULL) sPSActionDescriptor->Free(descriptor);
if (reference != NULL) sPSActionReference->Free(reference);
return error;
and wrote aeta resource:
resource 'aete' (16000, "myFile" " dictionary", purgeable)
1, 0, english, roman,
vendorName,
"description",
plugInClassID,
1,
1,
vendorName " myFormat",
plugInAETEComment,
plugInClassID,
plugInEventID,
NO_REPLY,
IMAGE_DIRECT_PARAMETER,
"create",
keyMyCreate,
typeMyCreate,
"create type",
flagsEnumeratedParameter
typeMyCreate,
"layer",
createLayer,
"make layer"
And what now? Is any better examples?

How to enable debug mode?

Hi
We are doing some web dynpro development.
Can anyone tell me ho to enable debug mode in the server
Thanks
Vijay

Hi,
Check this blog, for some idea how to use configtool to set debug mode:
NetWeaver Portal Debugging
How to enable debug mode?
I see that you are new to this forum, first of all welcome to SDN.
I see that you have posted alot of questions today, really appreciate your interest in learning new stuff.
SDN is a great forum to start with but my suggestion is to first search the forum for answers to your questions before posting them, this way you will help yourself instead of waiting for people to help you out.
Greetings,
Praveen Gudapati
[Points are always welcome for helpful answers]

Problem calling C# dll using JNI

Hi,
I'm trying to call C# functions from a JNI interface. I built a C++ DLL to link the Java and C# calls together, but I am always getting the same error. Calling the C# DLL directly from the C++ code (compiled as an application) does not cause this error. I have to be able to connect our java application with a third party C# DLL, so I cannot just right the DLL directly in C++... Here is my code:
//C# Class Library::
namespace ClassLibrary2
     /// <summary>
     /// Summary description for Class1.
     /// </summary>
     public class Class1
          public Class1()
               // TODO: Add constructor logic here
          public void Bidon1()
     MessageBox.Show("Affiche", "Toi", MessageBoxButtons.OK, MessageBoxIcon.Exclamation);
//C++ DLL::
#using "ClassLibrary2.dll"
BOOL APIENTRY DLLMain(HANDLE hModule, DWORD ul_reason_for_call, LPVOID lpReserved) {
return TRUE;
JNIEXPORT void JNICALL Java_com_blablabla_CommJNIDLL_Init
(JNIEnv * enivronmt, jobject obj)
     new ClassLibrary2::Class1();
     (new ClassLibrary2::Class1())->Bidon1();
Olivier dit :
//Java JNI Calls::
//From CommJNIDLL::
     static {
          System.loadLibrary("MyCDLL");
     public native void Init();     If I comment the calls within the C++ DLL, they get fired, and no exception is raised. What am I doing wrong?
Thanks, bumpert

Hi,
I am currently also trying to call some C# code within JNI. So far I have managed to call some simple C# code in Java through JNI based on the example on codeproject. However, now my problem is that instead of doing JNI-->C++->M C++->C#, I need to include one more reference to some other DLLs in the C# code. Therefore I need to do JNI-->C++-->M C++-->C#-->DLL. So is there a way to do this? I can compile all the code sucessfully in C++, but when I try to execute the .netmodule (for C#) and DLL for C++ through JNI in Java, it gives me an error. I have tried to put all the relevant DLLs in the same directory, but it still does not work. So is there someway to combine the .netmodule of C# with the DLLs it references to? Perhaps that could solve the problem? I am new to C# and C++, really appreciate if someone can give some advices since there's nothing much on the net.
thanks,
Lee

Calling COM DLLs using JNI

I am able to call ordinary dlls from my java application using JNI, by exporting the function from my DLL.
What can I do to call COM DLLs using JNI which do not expose the
Functions directly.
please help!
thanx,
-sachin

Is this a COM dll that you have written or do you merely have the dll?
If you merely have the dll, there are some third party tools that will generate Java interfaces to COM objects from the dll.
Although I don't endorse these products or work for them I've used them before with some success:
o J-Integra -- http://www.intrinsyc.com/
o jacoZoom -- http://www.infozoom.de/
-- rob

VS2013 not running in debug mode on Windows 10 Technical Preview Build 10041

am getting the following errors every time i try to run my projects in debug mode what can be the issue.
Managed Debugging Assistant 'FatalExecutionEngineError' has detected a problem in 'C:\Program Files (x86)\IIS Express\iisexpress.exe'.
Additional information: The runtime has encountered a fatal error. The address of the error was at 0x73c0d5a5, on thread 0x1a0c. The error code is 0xc0000005. This error may be a bug in the CLR or in the unsafe or non-verifiable portions of user
code. Common sources of this bug include user marshaling errors for COM-interop or PInvoke, which may corrupt the stack.
Then when I continue the following appears
An unhandled exception of type 'System.AccessViolationException' occurred in System.Data.dll
Additional information: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
Then it stops..
This happens when a database call is made and only does this when debug, when I run it using the browser link all is good. The applications work well.

Hi Bigmachini,
According to my solution, what about your issue now?
If you have been solved the issue, would you mind sharing us the solution here? So it would be helpful for other members who get the same issue.
If not, please let us know the latest information about it.
@Malik, could you please tell me if you try to check your issue by the above suggestion as I said?
If no, please try the above suggestions to check this issue and then tell me the latest message about this issue.
>>The error mostly occurs when debugging ADO.NET or database function calls. If code is run without debugging then there is no issue at all.
You could also try to copy your project and then debug your project in debug mode on a another machine you install same Windows 10 OS check this issue again.
Best Regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Call labview dlls in release mode

Hi all,
I built a LabVIEW dll for the bluetooth connection, at the beginning I called this dll in the VS C++ in the debug mode, it worked very well.
but due to the application, all the code should run in release mode. Unfortunately error occured, " Runtime error, R6030 CRT not initialized".
I googled, but i did not get something useful.
I appreciate any comments and information, and apologize for my poor english.
ps. I tried to use different runtime library, and finially I got only multi-thread DLL was suitable.

the attachments are the VC code and the dll files,
I really appreciate any comments about thie problem.
Attachments:
bluetooth test.zip ‏869 KB
lib.zip ‏340 KB

Error 1073 when building LabVIEW app which calls LabVIEW dll

I am trying to use application builder to build an application that calls a dll created in LabVIEW. I get an error referencing a vi within the dll (Parse Stored String(multibyte).vi) saying that "This property is writable or this method is available only when the VI is in edit mode." The only option is to Continue which cancels the build. I had sucessfully built this application prior to including vis that call the dll and the program runs fine in the development environment.
Do you have any idea what is causing this and what I cam do about it?

I have found a temporary workaround in which I created a dummy dll that removed all functionality from exported vis but had the same name and function signatures. I then built the application using this dummy dll. Once complete, I replaced the dummy dll with the real dll.
This is not a satisfactory work around because we have to build and maintain two dlls. Also, I'm not sure we can do the same trick when creating the installer with application builder. So, I'd still appreciate any help you can give.

Call function in debug mode

Hi,
when I´m on the test function screen of se37, I can run the function in debugging mode and it´s starting with the debugger on the first code line.
Is it also call a function from a report in this debugging mode?
thank you!
reward points guaranteed

Thank you for your answers...
Let me explain a little bit more in detail, what I want to do.
I have an XML interface function which is going to be called by an
external application about RFC, reading binary data,
interpreting that as XML and doing something in the SAP system afterwards.
As the system is a 4.6C I can´t debug externally, I want to provide
a debugging function in a monitoring application for that.
As people are using the monitoring, which are not familiar with all
the code behind that, I want to start the debugging mode by myself,
without setting a breakpoint.
Let me describe it like this:
When you type in /H in the transaction field in the SAP menu bar, the
debugging mode is going to be started for further actions.
All I want to do is starting that /h debug mode without typing anything
in the transaction field, just inside of the report.
How can I do that?
Michael

DLL build by Labview App Builder doesn't work if Built-IN functions used!?

Hi All,
I hope somebody shed some light on this;
(All VIs are in the attached case1-2.zip)
Case 1:
A VI reads a 1D array data and Uses RMS.vi to calc the rms of the data and returns the rms value and the error value. (make1_dll.vi).
This VI is used to build a DLL. (test1.dll using the test1.bld)
Call this DLL in a new VI (just to test that the DLL works) (test1.vi)
RUN the new VI >>> Result Nothing happens No Error or Crash and No result!!!
Case2 :
Build the above without using the “RMS.vi” and works OK. (see case2 VIs)
Any idea why the build-in function doesn’t work?
Best regards
Attachments:
case1-2.zip ‏44 KB

Joel A wrote:
You might want to look at the path building you are doing to find the RMS VI. If you are using relative paths, then LabVIEW calls like "VI Path" will have an extra path if the VI is an exe or inside an LLB.
Drop some probes (indicators, outputs, etc.), rebuild and double check the paths. I've been burned by this before...
If this is the case, you can use the VI properties, or path parsing to solve it.
joel
I don't think that is the problem. The RMS.vi is referenced as statically linked VI in the make1_dll.vi.
As such it should be linked into the LabVIEW DLL as well. What I suspect is the problem is the fact that
the RMS.vi uses the lvanlys.dll and that for some reason there is something going wrong with the LabVIEW
test1.dll, which runs in the LabVIEW runtime context, calling lvanlys.dll while executed in the context
of LabVIEW itself. Probably something to do with the changes to how lvanlys.dll is treated between LV 7.0
and 7.1.
I see this same behaviour on my system too, so an installation problem is quite unlikely. Other than that calling a LabVIEW dll from within LabVIEW makes not that much sense (but did work fine in the past save from some hassles in 6.0 and 6.0.1), I have no explanation why this doesn't work.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Dll issue, works in release.exe but not in debug mode.

I have an issue with a dll that was previously working in both released and in debug mode. Now if I create a released .exe it functions. If I run it in debug mode the call to the dll function never returns. eventually whatever is occurring behind the scense prevents the released.exe from working also. I do not know if I accidenatally changed a setting in the cvi compiler that broke the code. Is there a way to default cvi2010 settings?

You can go back to the default ADE settings by renaming the following registry key to something else (anything other than "10.0", it doesn't matter what):
[HKEY_CURRENT_USER]\Software\National Instruments\CVI\10.0.
I think it's best to rename it, rather than delete it, so that you can go back to your current settings any time you choose to. Make sure CVI is not running when you rename the key.
After the rename, the first time you run CVI, it will prompt you if you want to copy the settings. Say no to that. At that point, CVI will create a new "10.0" key with the default settings in place.
Once you're done with your investigation, if you prefer to go back to the settings you had, you can delete the new 10.0 and rename the previous key back to "10.0".

How to transfer data between a multi-thread dll build with LV7 and MS C++, using envent programing method.

It is easy to transfer data between a simple input/output dll build with LV and an external code like C++, but when data are available inside a loop running in the dll(in fact thread running in LV); How can I read them or receive an handle pointer to the calling C++ application when new data are ready.

If you're using LabVIEW 7, you can use the PostLVUserEvent function to fire an event for an event structure in LV. Refer to the Using External Code in LV manual.
Or you could use datasocket for this. The datasocket activex dll is nids.dll. You could have the class wizard generate wrappers for you or if you have Measurement Studio, you could use the custom wrappers it provides to communicate between the VI and dll.
I hope this helps
Bilal Durrani
NI
Bilal Durrani
NI

Calling a function from a DLL, exectution in background mode.

Dear Experts,
We have created an ABAP report the calls a function from a DLL file. If the report is executed in on-line mode the program calls and executes the function from the DLL, but if the ABAP programa is executed in background mode it doesnt calls the DLL function.
Do you know a way to solve the problem when executing in background mode?
Best regards.
Antonio

Hi Gabriel,
Let me explain in details about my DLL function.
We are importing the business partners from legacy system into the SAP CRM system, so at the moment we created the BP master data via BAPI, I get the name of the BP and this moment I call the function in the DLL file. I export the parameter name and I receive back a simplified string with the name reduced to a code. This code I get back from the dll it is insert in a Z table, so there is no interaction in the screen, all must be executed in background mode, because there are a lot of business partners to be converted in SAP system.
I am sending my code for your considerations.
Instancia a DLL
CREATE OBJECT dll 'MTCODE.CPFONET'.
IF sy-subrc NE 0.
    RAISE without_dll.
ENDIF.
Move para a tabela interna IT_NAME os valores recebidos na TI_NAME
it_name[] = ti_name[].
Para cada registro importado
LOOP AT it_name.
    CLEAR v_string_ret.
    wa_matchcode-zregid     = it_name-zregid.
    wa_matchcode-name1_text = it_name-name1_text.
    v_string = it_name-name1_text.
    CONDENSE v_string.
    TRANSLATE v_string TO UPPER CASE.
    CALL METHOD OF dll 'SetNome' EXPORTING #1 = v_string.
    CALL METHOD OF dll 'ExecMatch'.
    CALL METHOD OF DLL 'GetMCData' = v_string_ret.
    FREE OBJECT dll.
Preenche os campos do match-code de acordo com o retorno da DLL
    SPLIT v_string_ret
    AT '|'
    INTO wa_matchcode-zparmcln
         wa_matchcode-zparmcfn
         v_empty
         wa_matchcode-name_first
         wa_matchcode-name_last
         wa_matchcode-namemiddle.
Adiciona o registro com o match-code correspondente na TE_MATCHCODE
    APPEND wa_matchcode TO te_matchcode.
ENDLOOP.

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.

How to find out User Id Used in Debugging Mode

Hi Gurus
Could you plz advice . how find to out SAP user Id used to delete SAP table entries in Debugging Mode.
Thanks
Ravi

Hi Ravikanth,
I'm not sure how to check the change log in debugging mode,
but you can get the LOG DATA CHANGES from tcode SCU3(If log checkbox selected in Technical settings).
You may check the coding for scu3 for more details.
Happy coding..!!
//Kiran Singh

JNI calls using dll build in DEBUG mode

Similar Messages

Maybe you are looking for