JDev in Debugging Mode

Hi,
Im running the application in debug mode. after which i updated a java file and compiled it. Now when i reload the page(didnt restart the server instance), i am getting classnotfound exception.
Is this a standard behaviour of Jdev or when i reload the page should the latest file should get picked?
Thanks,
Viswanath

Timo,
Sorry in my previous post ,i meant to say that i have to rerun the application.Should i rerun the application even if i change any property in .jspx page?
When i change the existing java file and reopen the target url, sometimes it picks the latest file and sometimes it gives IllegalStateException.
Could you please explain what changes get reflected immediately and when should i rerun the application.
In one of the forum post there was suggestion to set the below property. When i tried this application didn't recognize the class files even when i rerun.
Tools->Preferences->Run->WebLogic and setting Select Hot Class Reload Policy to Fast Swap
Thanks,
Viswanath

Similar Messages

How do debug an application in Shared Memory debug mode using JDev

I don't see the option of using "Shared memory" debug mode in JDev. There is only socket debug option(Attach/Listen) in debugger but no shared memory debug option.
Is it missing or is it hidden somewhere.
Can anyone let me know as all IDEs provide that.

Any updates?

JApplet run in Debug mode but not in Run Mode in JDev3.1

Hi All
I am having a problem in running a JSP file which contain an JApplet. When I choose Run from the jDev, the applet seems to take a really long time to load and finally failed to load itself.
However when i choose run from debug mode, the jsp run perfectly by displaying the applet.
Any idea why?
thanks for any help
ka

Hi All
I am having a problem in running a JSP file which contain an JApplet. When I choose Run from the jDev, the applet seems to take a really long time to load and finally failed to load itself.
However when i choose run from debug mode, the jsp run perfectly by displaying the applet.
Any idea why?
thanks for any help
ka

Android Emulator get hangs on starting the application in debug Mode

I have deployed the application on Android Emulator in debug mode but on starting the app it get hangs. I have set the Java Debugging to true in the cvm.properties file and also started Java debugger from JDev before launching the ADF Mobile app on android emulator. Can any body help me to figure out the problem why the emulator gets hang on starting the application in debug Mode.

Hi, after setting the debugging = true, you would also need to start the JDeveloper debugger and configure it for remote debugging. Shay has a blog article that should help.
The emulator is hung while trying to connect to the JDeveloper debugger.
https://blogs.oracle.com/shay/entry/debugging_adf_mobile_apps_on
Thanks,
Joe Huang

Running applications in debug mode in JDeveloper

Hi All,
I have created a simple spring portlet and have consumed it on a webcenter application. The portlet throws an exception. Now I want to run my portlet in debug mode.
Both webcenter application and portlet producer are running on the jdeveloper integrated server.
Can any one help me out mentioning steps to run the portlet and the portal app in debug mode.

Some info can be found in this thread in JDev forum: JDeveloper remote debugging OC4J
However, it is based on 10g and OC4J. Still, I believe, the overall concept can be used.

Reset Preference for Launch in Debug Mode

I accidently clicked "Don't ask me again" when queried whether I want to always launch in debug mode when I debug. How can I reset that. The obvious place under Run/Debug in preferences didn't work for me.

Hi Jeff,
I'm assuming that you are using JDev 9.0.3.
Make sure that your project has the "Oracle JDBC" library selected. This can be done on the Libraries panel of the Project Settings dialog box.
Are you saying that you get the ClassNotFoundException when you step through your program in debug mode, but when you run you program it works fine?
-Liz

Problem when trying to run in "Debug Mode" in JDeveloper9i

Hello All ,
i have a problem to debug my application using
JDeveloper9i .
i get an error: "fdebug.exe could not be read "
and Application error box appears .
i did the following steps in the instalation:
1) i installed the JDK 1.3
2) installed the Jdev9i from base installation zip
3) In <jdeveloper_root>\jdev\bin\ i executed the command
InstallOJVM.bat c:\jdk1.3
and get message:
"InstallOJVM successfully"
4) i wrote simple program and put a breakpoint ,
when i'm trying to run the program in "Debug mode" i get an error box message
"fdebug.exe Application Error"
The memory instruction could not be read
please help ,me to fix the problem i need the debuger option .
thanks in advance.

Do you have the file c:\jdk1.3\jre\bin\fdebug.exe, if you don't, you
need it. Look for the file in the base install directory, it should be
there and then copy it to the location above.
Michel

Error when starting Weblogic in debug mode

Hi there
Has anyone experienced any difficulties when starting weblogic in debug mode.
More specifically, it cannot start correctly because it thinks that another instance
is using the same port (definately not the case).
Any clues/suggestions are greatly appreciated.
Error log follows:
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Emergency> <WebLogicServer> <Unable to create
a server socket for port: 8320. java.net.BindException: Address already in use
Perhaps another process is using port 8320.>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Notice> <WebLogicServer> <SSLListenThread
listening on port 8321>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Emergency> <WebLogicServer> <The WebLogic
Server is no longer listening for connections. You should probably restart it.>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Alert> <WebLogicServer> <Server shutdown
has been requested by system>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Alert> <WebLogicServer> <The shutdown sequence
has been initiated.>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Info> <WebLogicServer> <Server shutdown is
commencing NOW and is irreversible.>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Error> <Performance Pack> <Unable to load
performance pack, using Java I/O.
java.lang.ThreadDeath
at java.lang.Thread.stop(Thread.java:581)
at weblogic.t3.srvr.T3Srvr.die(T3Srvr.java:764)
at weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:507)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:171)
at weblogic.Server.main(Server.java:35)

Thanks for the suggestion.
Unfortunatley the port is definately free/available during startup.
Stephane Kergozien <[email protected]> wrote:
Maark,
Before starting your server, please could you check that the port is
not used by one
other process. You can use the netstat command to do this.
Regards
Stephane
Mark wrote:
Hi there
Has anyone experienced any difficulties when starting weblogic in debugmode.
More specifically, it cannot start correctly because it thinks thatanother instance
is using the same port (definately not the case).
Any clues/suggestions are greatly appreciated.
Error log follows:
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Emergency> <WebLogicServer> <Unableto create
a server socket for port: 8320. java.net.BindException: Address alreadyin use
Perhaps another process is using port 8320.>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Notice> <WebLogicServer> <SSLListenThread
listening on port 8321>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Emergency> <WebLogicServer> <TheWebLogic
Server is no longer listening for connections. You should probablyrestart it.>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Alert> <WebLogicServer> <Servershutdown
has been requested by system>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Alert> <WebLogicServer> <The shutdownsequence
has been initiated.>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Info> <WebLogicServer> <Servershutdown is
commencing NOW and is irreversible.>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Error> <Performance Pack> <Unableto load
performance pack, using Java I/O.
java.lang.ThreadDeath
at java.lang.Thread.stop(Thread.java:581)
at weblogic.t3.srvr.T3Srvr.die(T3Srvr.java:764)
at weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:507)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:171)
at weblogic.Server.main(Server.java:35)--
Regards,
Stephane Kergozien
BEA Support

Can't Run program in Debug Mode

To: [email protected]
cc:
Subject: Can't Run program in Debug Mode
Has anyone else experienced this problem? We have written a non-express
program that uses the Express generated services project as a supplier
plan. However, when we try running this program in debug mode about 50%
(or more) of the time we abend while Forte is trying to partition the
application. Since we have many database classes in our Business Model we
are wondering if Forte is timing out during the partition phase or if the
server partition is running out of memory . The following error messages
are produced by Forte. Any suggestions???
=======================
Error messages on client:
=======================
SYSTEM ERROR: Unable to start the partition testacadprogoffer_CL0_Part1 on
any
of the nodes to which it has been assigned. See the remainder of the
error
stack for more information.
Class: qqsp_ResourceException
Error #: [1602, 593]
Detected at: qqcf_StandardConfig::LoadRemotePartition at 5
Last TOOL statement: method overview.StartApplication
Error Time: Tue Dec 02 12:56:01
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
SYSTEM ERROR: Unable to start partition testacadprogoffer_CL0_Part1 on node
admin2.
Class: qqsp_ErrorDescriptor
Error #: [1602, 592]
Detected at: qqcf_StandardConfig::LoadRemotePartition at 3
Error Time: Tue Dec 02 12:56:01
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
SYSTEM ERROR: Lost contact with remote server while trying to load
partition
testacadprogoffer_CL0_Part1. Check server log file for more information
about
the specific problem.
Class: qqsp_ResourceException
Error #: [1301, 102]
Detected at: qqem_IPartitionAgent::Startup at 5
Error Time: Tue Dec 02 12:56:01
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
INFORMATION: The connection to the partner was terminated by the
Communication
Manager for the reasons below.
Class: qqsp_DistAccessException
Detected at: qqdo_PartitionMgr::StopLocation at 1
Error Time: Tue Dec 02 12:56:00
Distributed method called: qqrt_ForteExecAgentProxy.LoadPartition!6
(object name Unnamed) from partition "Forte_Executor", (partitionId =
F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9, taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9.229]) in application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment CentralEnv
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
INFORMATION: Network partner closed connection. This usually means the
process at the other end of the wire failed. Please go look there and
find
out why.
Class: qqsp_DistAccessException
Detected at: qqcm_HoseFSM::ReceivedClose at 2
Error Time: Tue Dec 02 12:56:00
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
INFORMATION: Received close: Connection aborted (10053).
Class: qqsp_DistAccessException
Detected at: qqcm_HoseFSM::ReceivedClose at 1
Error Time: Tue Dec 02 12:56:00
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
=======================
Log messages on server:
=======================
Attached to manager for node admin2.
aud Tue Dec 2 09:34:36 : Loading partition testacadprogoffer_cl0_Part2
built on <unknown>.
Attached to manager for node admin2.
aud Tue Dec 2 09:41:58 : Shutting down partition as requested.
aud Tue Dec 2 09:41:59 : Unloaded partition testacadprogoffer_cl0_Part2.
aud Tue Dec 2 09:49:44 : Loading partition testacadprogoffer_cl0_Part2
built on <unknown>.
Attached to manager for node admin2.
aud Tue Dec 2 10:00:11 : Shutting down partition as requested.
aud Tue Dec 2 10:00:12 : Unloaded partition testacadprogoffer_cl0_Part2.
aud Tue Dec 2 10:18:34 : Loading partition testacadprogoffer_cl0_Part3
built on <unknown>.
Attached to manager for node admin2.
aud Tue Dec 2 10:27:00 : Shutting down partition as requested.
aud Tue Dec 2 10:27:00 : Unloaded partition testacadprogoffer_cl0_Part3.
aud Tue Dec 2 10:47:03 : Loading partition
EvaluateApplRequirementsBO_CL0_Part1 built on <unknown>.
Attached to manager for node admin2.
aud Tue Dec 2 11:09:26 : Shutting down partition due to failure of agent
owner's partition.
aud Tue Dec 2 11:09:26 : Shutting down partition as requested.
aud Tue Dec 2 11:09:26 : Unloaded partition
EvaluateApplRequirementsBO_CL0_Part1.
aud Tue Dec 2 12:36:14 : Loading partition testacadprogoffer_CL0_Part1
built on <unknown>.
Attached to manager for node admin2.
aud Tue Dec 2 12:45:17 : Shutting down partition as requested.
aud Tue Dec 2 12:45:17 : Unloaded partition testacadprogoffer_CL0_Part1.
FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
Task 11: qqcm_HoseRecvServiceTask::Run: Caught unexpected exception
FATAL ERROR: ************* Out of Memory, requested (1K) available (0K)
Class: qqsp_ResourceException with ReasonCode: SP_ER_OUTOFMEMORY
Detected at: qqos_MemoryManager
Error Time: Tue Dec 2 12:49:01
Exception occurred (locally) on partition "Forte_Executor",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10f3, t
askId = [F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10f3.11]) in application
"Forte Runtime", pid 14020 on node admin2 in environ
ment CentralEnv.
FATAL ERROR: ************* Out of Memory, requested (1K) available (0K)
Class: qqsp_ResourceException with ReasonCode: SP_ER_OUTOFMEMORY
Detected at: qqos_MemoryManager
Error Time: Tue Dec 2 12:48:57
FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
ERROR: TMgr.RunThread: task cm.Recv failed terminating.
Probably caused by a FATAL exception.
David Wilbur email: [email protected]
University of Windsor phone: 519-253-3000 ext. 2779
Windsor, Ontario Canada
-----------------------------------------------

Hi,
We have had the same problem in a non-express application
with a heavy server partition. In our case, the error was not
systematic, depending on the server workload at the time we
tried to partition and run.
The work-around we're using is to put the -fm flags (increasing the x
parameter to say 30000) in the 'server arguments' of your server
partition
properties in the partition workshop. Note that if your server is a Unix
platform,
you need to put double-quotes before and after the parenthesis in the -fm
syntax.
Hope this helps,
Vincent Figari
BTW, what Forte version are you using ?
On Tue, 2 Dec 1997 13:44:24 -0500 "David Wilbur"<[email protected]>
writes:
>
>
>
>
>
To: [email protected]
cc:
Subject: Can't Run program in Debug Mode
Has anyone else experienced this problem? We have written a
non-express
program that uses the Express generated services project as a supplier
plan. However, when we try running this program in debug mode about
50%
(or more) of the time we abend while Forte is trying to partition the
application. Since we have many database classes in our Business
Model we
are wondering if Forte is timing out during the partition phase or if
the
server partition is running out of memory . The following error
messages
are produced by Forte. Any suggestions???
=======================
Error messages on client:
=======================
SYSTEM ERROR: Unable to start the partition
testacadprogoffer_CL0_Part1 on
any
of the nodes to which it has been assigned. See the remainder of
the
error
stack for more information.
Class: qqsp_ResourceException
Error #: [1602, 593]
Detected at: qqcf_StandardConfig::LoadRemotePartition at 5
Last TOOL statement: method overview.StartApplication
Error Time: Tue Dec 02 12:56:01
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in
application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
SYSTEM ERROR: Unable to start partition testacadprogoffer_CL0_Part1 on
node
admin2.
Class: qqsp_ErrorDescriptor
Error #: [1602, 592]
Detected at: qqcf_StandardConfig::LoadRemotePartition at 3
Error Time: Tue Dec 02 12:56:01
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in
application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
SYSTEM ERROR: Lost contact with remote server while trying to load
partition
testacadprogoffer_CL0_Part1. Check server log file for more
information
about
the specific problem.
Class: qqsp_ResourceException
Error #: [1301, 102]
Detected at: qqem_IPartitionAgent::Startup at 5
Error Time: Tue Dec 02 12:56:01
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in
application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
INFORMATION: The connection to the partner was terminated by the
Communication
Manager for the reasons below.
Class: qqsp_DistAccessException
Detected at: qqdo_PartitionMgr::StopLocation at 1
Error Time: Tue Dec 02 12:56:00
Distributed method called:
qqrt_ForteExecAgentProxy.LoadPartition!6
(object name Unnamed) from partition "Forte_Executor",
(partitionId =
F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9, taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9.229]) in
application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in
application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
INFORMATION: Network partner closed connection. This usually means
the
process at the other end of the wire failed. Please go look there
and
find
out why.
Class: qqsp_DistAccessException
Detected at: qqcm_HoseFSM::ReceivedClose at 2
Error Time: Tue Dec 02 12:56:00
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in
application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
INFORMATION: Received close: Connection aborted (10053).
Class: qqsp_DistAccessException
Detected at: qqcm_HoseFSM::ReceivedClose at 1
Error Time: Tue Dec 02 12:56:00
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in
application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
=======================
Log messages on server:
=======================
Attached to manager for node admin2.
aud Tue Dec 2 09:34:36 : Loading partition
testacadprogoffer_cl0_Part2
built on <unknown>.
Attached to manager for node admin2.
aud Tue Dec 2 09:41:58 : Shutting down partition as requested.
aud Tue Dec 2 09:41:59 : Unloaded partition
testacadprogoffer_cl0_Part2.
aud Tue Dec 2 09:49:44 : Loading partition
testacadprogoffer_cl0_Part2
built on <unknown>.
Attached to manager for node admin2.
aud Tue Dec 2 10:00:11 : Shutting down partition as requested.
aud Tue Dec 2 10:00:12 : Unloaded partition
testacadprogoffer_cl0_Part2.
aud Tue Dec 2 10:18:34 : Loading partition
testacadprogoffer_cl0_Part3
built on <unknown>.
Attached to manager for node admin2.
aud Tue Dec 2 10:27:00 : Shutting down partition as requested.
aud Tue Dec 2 10:27:00 : Unloaded partition
testacadprogoffer_cl0_Part3.
aud Tue Dec 2 10:47:03 : Loading partition
EvaluateApplRequirementsBO_CL0_Part1 built on <unknown>.
Attached to manager for node admin2.
aud Tue Dec 2 11:09:26 : Shutting down partition due to failure of
agent
owner's partition.
aud Tue Dec 2 11:09:26 : Shutting down partition as requested.
aud Tue Dec 2 11:09:26 : Unloaded partition
EvaluateApplRequirementsBO_CL0_Part1.
aud Tue Dec 2 12:36:14 : Loading partition
testacadprogoffer_CL0_Part1
built on <unknown>.
Attached to manager for node admin2.
aud Tue Dec 2 12:45:17 : Shutting down partition as requested.
aud Tue Dec 2 12:45:17 : Unloaded partition
testacadprogoffer_CL0_Part1.
FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
Task 11: qqcm_HoseRecvServiceTask::Run: Caught unexpected exception
FATAL ERROR: ************* Out of Memory, requested (1K) available
(0K)
Class: qqsp_ResourceException with ReasonCode: SP_ER_OUTOFMEMORY
Detected at: qqos_MemoryManager
Error Time: Tue Dec 2 12:49:01
Exception occurred (locally) on partition "Forte_Executor",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10f3, t
askId = [F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10f3.11]) in
application
"Forte Runtime", pid 14020 on node admin2 in environ
ment CentralEnv.
FATAL ERROR: ************* Out of Memory, requested (1K) available
(0K)
Class: qqsp_ResourceException with ReasonCode:
SP_ER_OUTOFMEMORY
Detected at: qqos_MemoryManager
Error Time: Tue Dec 2 12:48:57
FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
ERROR: TMgr.RunThread: task cm.Recv failed terminating.
Probably caused by a FATAL exception.
David Wilbur email: [email protected]
University of Windsor phone: 519-253-3000 ext. 2779
Windsor, Ontario Canada

Can not view contents of variable in debug mode (version 1.1.1.5.0)

Hi
I am running on WebLogic 11R1 and using OEPE 1.1.1.5.0.
When Fast swap is enabled and I run WebLogic in debug mode using OEPE I can not view the contents of variables with the Eclipse debugger. I get the message "Expressions must contain either an expression or a block containing a well formed statement"
However, if I disable Fast swap, i can view the variable within the Eclipse debugger
Has anyone else had this problem?
Regards
Steve H

Small correction... the soon-to-be-released version of WebLogic Server that Danny was referring to is 11gR1 PatchSet 2 or 10.3.3.

FlashBuilder 4.7 will not run in Debug mode with BlackBerry 10 simulator

We have developed an app that has been released both for Apple and Android working well.
When trying to do the same for BlackBerry it was rejected because it did not start at all.
The App that runs fine on the BlackBerry simulator in the "run configurations mode".
However when I try to run it in Debug mode it will not start at all. Just flashes and simulator goes back to main menu.
The debugger will after a while time out since it cannot connect to the app running on the simulator.
BlackBerry 10 Simulator runs under vmWare Fusion.
Anyone seen this before?

Hi, Silence04. Welcome to the Discussions.
You had serious disk directory corruption. That can also cause corruption in OS files: while Disk Utility or DiskWarrior may fix the directory, if the directory corruption resulted in OS files being damaged — as it appears to be in this case — then you can't avoid an Archive and Install. For important tips on this, see my "General advice on performing an Archive and Install" FAQ. Perform the steps therein in the specified order.
Good luck!
Dr. Smoke
Author: Troubleshooting Mac® OS X
Note: The information provided in the link(s) above is freely available. However, because I own The X Lab™, a commercial Web site to which some of these links point, the Apple Discussions Terms of Use require I include the following disclosure statement with this post:
I may receive some form of compensation, financial or otherwise, from my recommendation or link.

SRM 7.0 - Unable / How to get into DEBUGGING mode in BADI

Hello SAPions,
I am unable to get into debugging mode from WebDynpro Portal screen to R/3 BADI in SRM 7.0 .
I placed a breakpoint in the BADI, and logged into the portal screen.
However, in SRM5.0, to get into debugging mode from ITS, we place a break point in the BADI, when we browse the ITS link from the IE browser, we will be able to get into debuggin mode.
Any other way ?
Regards,
Ashwin.

Hello,
Please check the following:
1. Application server name, the SAP GUI and the portal should be logged into the same application server.
2. You should be logged in with the same User in both SAP GUI and the Portal.
3. External debugging should be enabled for the User in SAP GUI.
4. Also try checking the check box , IP Matching . This can be done as below:
Utilities -> Settings -> ABAP Editor -> Debugging -> IP Matching.
Also please check the following in the above link , if you have the same user name here with which you have logged onto Portal and the New Debugger Radio Button is Selected.
Hope this helps.
Best Regards,
Sapna

How to fill internal table with no data in debugging mode

Hi all,
I modified one existing program.Now I want to test it.I am not given test data.So in the middle of my debugging, I found that one internal table with no data.My problem is how to fill that internal table with few records in that debugging mode just as we change contents in debugging mode.If I want to proceed further means that internal table must have some records.
Please I dont know how to create test data so I am trying to create values temporarily in debugging mode only.
Thanks,
Balaji

Hi,
In the debugging do the following..
Click the Table button..
Double click on the internal table name..
Then in the bottom of the screen you will get the buttons like CHANGE, INSERT, APPEND, DELETE..
Use the APPEND button to insert records to the internal table..
Thanks,
Naren

How to start the server in debug mode

HI
Im working on weblogic server 8.1 sp. My requirement is to run the application in hosted on weblogic server with out restaring the server i.e dynamiically turn to debug mode with out stopping. IM using Log4j method for logging. please let me know how to do it... if any one have sample java code
Thanks & regards
shiva

I am not sure, how can you do it on the fly, but if you want to restart the server here are the parameters you need to add to the java arguments
-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=$Port
(where Port will be any port you want to connect to).
Thanks
Togotutor
<b><a class="jive-link-external" href="http://www.togotutor.com">http://www.togotutor.com</a> (Learn Programming and Administration for Free)</b>
Edited by: togotutor on Aug 12, 2010 3:44 PM

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.

JDev in Debugging Mode

Similar Messages

Maybe you are looking for