Compiling with debug option

How to give user Compiling with debug option, i have try to by giving grant debug any procedure and debug connect session but it failed.
Any ideas?
Edited by: rootsman on Jul 15, 2010 12:00 AM

Post the error screenshot..
eg:
grant DEBUG CONNECT SESSION to username;
grant DEBUG ANY PROCEDURE to username;
Check the below explanation:
DEBUGGING:
DEBUG CONNECT SESSION
Connect the current session to a debugger that uses the Java Debug Wire Protocol (JDWP).
DEBUG ANY PROCEDURE
Debug all PL/SQL and Java code in any database object; displayinformation on all SQL statements executed by the application
Note: Granting this privilege is equivalent to granting the DEBUG object privilege on all applicable objects in the database.

Similar Messages

How to determine if class was compiled with debugging information?

How may I determine if class was compiled with debugging information? Aside from actually executing the class in a debugger.

As known, when compiling "javac -g ..." the class
files contain debugging information.
my Naive question is WHAT is this information?
could you please add any links to articles about this
debugging information?http://java.sun.com/docs/books/vmspec/2nd-edition/html/ClassFile.doc.html#22856
http://java.sun.com/docs/books/vmspec/2nd-edition/html/ClassFile.doc.html#5956

Copied objects are compiled with debug True

I had an issue with copied packages/triggers/procedures that when they were copied showed up as compiled with debug status.
My sql developer client has a default setting of compilng PL/SQL code with optimization level = 0 , while our database has a default = 2.
When modifying this level and setting it to 0, the debug flag is turned on, although not specified in the sql developer client)
preferences -> database -> PL/SQL -> Optimization Level = 2
select * from v$parameter where name like 'plsql%' returns
888         plsql_debug      1             FALSE    FALSE
889         plsql_optimize_level     3             2             2 after setting the level to 0 the same query returns:
888         plsql_debug      1             TRUE     TRUE
889         plsql_optimize_level     3             0             0this compile with debug behavior is shown on oracle 10 and 11 databases.

I also have sqldeveloper version 3.2.20.09 and look up the value for optimizer in the preferences menu via preferences -> database -> PL/SQL (just as in my first message)
BTW I can still reproduce this issue (and 15 other dbas and developers at where I work) on both oracle 10 and 11.
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
PL/SQL Release 10.2.0.4.0 - Production
"CORE     10.2.0.4.0     Production"
TNS for Linux: Version 10.2.0.4.0 - Production
NLSRTL Version 10.2.0.4.0 - Production
and
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
PL/SQL Release 11.2.0.2.0 - Production
"CORE     11.2.0.2.0     Production"
TNS for Linux: Version 11.2.0.2.0 - Production
NLSRTL Version 11.2.0.2.0 - Production
BTW We've been using sqldeveloper here since version 2.x. We found a workaround by setting the value for Optimization Level to 2, although you might not reproduce the issue, I suggest to keep it for others, although it seems not many others experience this issue.

Packages compiled with debug info

Hi,
How do we check if a package has been compiled with DEBUG information or not?
The package could have been compiled like this:
ALTER PACKAGE pk1 COMPILE DEBUG
Is there any table that I can check?
Thanks in advance.
Sanal Krishnan

Is this a 10g feature?It seems only user_plsql_object_settings is new in 10g.
all_plsql_object_settings is available in 9i:
michaels> select * from dict where table_name like '%PLSQL%'
TABLE_NAME                     COMMENTS
ALL_PLSQL_OBJECT_SETTINGS      Compiler settings of stored objects acce
                               ssible to the user
1 row selected.
michaels> select name, type,plsql_debug from sys.all_plsql_object_settings where owner = 'SYSTEM'
NAME                           TYPE         P
DEF$_PROPAGATOR_TRIG           TRIGGER
REPCATLOGTRIG                  TRIGGER
michaels> select * from v$version
BANNER
Oracle9i Enterprise Edition Release 9.2.0.8.0 - 64bit Production
PL/SQL Release 9.2.0.8.0 - Production
CORE     9.2.0.8.0     Production
TNS for HPUX: Version 9.2.0.8.0 - Production
NLSRTL Version 9.2.0.8.0 - Production

How to find out which PL/SQL Proc is Compiled with Debug?

Hi,
is there any View where i can see, which PL/SQL Proc is compiled with the debug flag?
Thanks
Marco
Message was edited by:
mpatzwah

Alternatively:
select name, plsql_debug from sys.all_plsql_object_settings

Problem in compiling with -g option

I am using forte5.1 compiler. While compiling my whole source code with -g option, for some of the files, the compilation is successfully but for some files I am getting en error as ">> Assertion (../link/dbg_stcomm.cc, line 271) while processing srsCallbacks.C at line 0. Error code 1. make:Fatal error". If I try to compile the whole source code without -g option my whole compilation is successfull. I have downloaded all the required patches for this. Previously I was using compiler 5.0 and I was not getting any error with -g option. Can u just tell me why am I facing this problem specifically with forte5.1 and not with 5.0. How can I resolve this problem so as to compile the whole source code with -g option?

Hi,
I think you will need patch:
Patch-ID# 109490-01
Synopsis: C++ 5.1: Patch for Forte Development 6 C++ compiler
As it appears that you are hitting bug id # 4312608
"Assertion: (../links/dbg_stcomm.cc, line 271)"
Can you confirm whether you are having this patch by doing:
"CC -V" or "showrev -p"
Thanks,
Gopinath.
Sun - DTS.

Compiling with debug info

Hi!
I get a question about PL/SQl, How can I compile a Block PL/SQL with debug information, in SQL*Plus?
Thanks in Advance
- Pablo

From the symptoms you describe, it is possible that the shared library contains a bug, but it is more likely that the problem is in your code, passing bad data to the shared library.
The problem might be a compiler bug, but I think an error in your code is more likely.
For example, your code as written might have undefined behavior that works by accident when compiling without optimizing, but fails when the compiler improves the runtime code.
Some examples:
1. A classic MT programming error is failing to declare a variable volatile when it is shared by more than one thread. In each thread, the compiler assumes it can remember the value of the variable and not reload it between references.
2. "x = ++x + b;" Modifying a variable twice in an expression withtout sequence points has undefined behavior -- compiler optimization can affect the result.
3." foo(x, x+=3);" the order of evaluation of function arguments is unspecified, so the actual values passed to foo could depend on optimization.
With C++ 5.5, you get some warnings from system headers that you can't do anything about, which I suspect is why you have disabled some warnings. Unfortunately, you might be disabling warnings that you need to see. That is, some of the disabled warnings could point to invalid code that results in the program crash.
I suggest using w instead of w2 (to avoid uninteresting warnings), and fix your code to eliminate the warnings you get.
In the current compiler, C++ 5.7 in Sun Studio 10, we have made some adjustments to warnings to make w and w2 more useful. You should consider upgrading.You can get a 60-day free trial version here:
http://www.sun.com/software/products/studio/index.xml
Also get the current patches for it here:
http://developers.sun.com/prodtech/cc/downloads/patches/index.html

Can't find library when compiled with debugging

Hi all,
Compiling this code segment cannot find a library when using -g
bash-3.2$ cat tester.cc
#include <iostream>
#include <string>
using namespace std ;
static void
myRoutine()
string str= "this is in routine" ;
string str3 ;
str3 = str.substr(11,7) ;
if(str.substr(0,4) == "this") cout << "Have a hit" << endl ;
cout << "this is str3 - " << str3 << endl ;
int main(int argc, char **argv)
string str = "this is a test" ;
string str1, str2 ;
str1 = str.substr(0,4) ;
str2 = str.substr(10,4) ;
cout << "this is str1 - " << str1 << endl ;
cout << "this is str2 - " << str2 << endl ;
myRoutine() ;
return 0 ;
bash-3.2$ CC -g -o tester tester.cc
bash-3.2$ ldd tester
     libCstd.so.1 =>     /usr/lib/libCstd.so.1
     libCstd.so.1 (SUNW_1.4.2) =>     (version not found)
     libCrun.so.1 =>     /usr/lib/libCrun.so.1
     libm.so.2 =>     /usr/lib/libm.so.2
     libc.so.1 =>     /usr/lib/libc.so.1
If I comment out:
if(str.substr(0,4) == "this") cout << "Have a hit" << endl ;
bash-3.2$ cat tester.cc
#include <iostream>
#include <string>
using namespace std ;
static void
myRoutine()
string str= "this is in routine" ;
string str3 ;
str3 = str.substr(11,7) ;
// if(str.substr(0,4) == "this") cout << "Have a hit" << endl ;
cout << "this is str3 - " << str3 << endl ;
int main(int argc, char **argv)
string str = "this is a test" ;
string str1, str2 ;
str1 = str.substr(0,4) ;
str2 = str.substr(10,4) ;
cout << "this is str1 - " << str1 << endl ;
cout << "this is str2 - " << str2 << endl ;
myRoutine() ;
return 0 ;
bash-3.2$ CC -g -o tester tester.cc
bash-3.2$ ldd tester
     libCstd.so.1 =>     /usr/lib/libCstd.so.1
     libCrun.so.1 =>     /usr/lib/libCrun.so.1
     libm.so.2 =>     /usr/lib/libm.so.2
     libc.so.1 =>     /usr/lib/libc.so.1
Or if I remove -g:
bash-3.2$ cat tester.cc
#include <iostream>
#include <string>
using namespace std ;
static void
myRoutine()
string str= "this is in routine" ;
string str3 ;
str3 = str.substr(11,7) ;
if(str.substr(0,4) == "this") cout << "Have a hit" << endl ;
cout << "this is str3 - " << str3 << endl ;
int main(int argc, char **argv)
string str = "this is a test" ;
string str1, str2 ;
str1 = str.substr(0,4) ;
str2 = str.substr(10,4) ;
cout << "this is str1 - " << str1 << endl ;
cout << "this is str2 - " << str2 << endl ;
myRoutine() ;
return 0 ;
bash-3.2$ CC -o tester tester.cc
bash-3.2$ ldd tester
     libCstd.so.1 =>     /usr/lib/libCstd.so.1
     libCrun.so.1 =>     /usr/lib/libCrun.so.1
     libm.so.2 =>     /usr/lib/libm.so.2
     libc.so.1 =>     /usr/lib/libc.so.1
then I can run successfully
Any thoughts or hints?
bash-3.2$ CC -V
CC: Sun Ceres C++ 5.10 SunOS_i386 2008/07/10
Usage: CC [ options ] files. Use 'CC -flags' for details
bash-3.2$ uname -a
SunOS alpha 5.11 snv_86 i86pc i386 i86pc
Thanks,
Jim

Ack! Please ignore my earlier posting. I did not play close enough attention to details in your post. I apologize for the confusion. Let me start over:
The Studio Express release you have contains a newer version of the C++ runtime library libCstd.so.1 than is available yet in Solaris patches. We bump the internal version number when we add new interfaces. The internal version number of the Studio Express library is SUNW_1.3.2. The version of the latest release Solaris patch is SUNW_1.3.1.
Some new string class operator functions are in version SUNW_1.3.2. I think these are also defined as inline functions in the compiler headers. When you compile with -g, inlining is disabled, and you create a dependency on library version SUNW_1.3.2. (Compiling with -g0 allows function inlining, and might resolve your problem, but read on.)
We have not released a libCstd.so.1 with internal version SUNW_1.4.2, so I don't understand how that version number could appear in an error message. Did you really see that version, or is it a transcription error? For now, let's assume it is a transcription error.
When you compile and link with CC, the program gets a runpath pointing into the compiler installation area. At program run time, the loader looks for libraries in directories listed in the runpath, with /lib and /usr/lib as last resort. The "ldd" command reports what the runtime loader will do regarding dependent libraries.
If the compiler is installed in /opt, a 32-bit program gets a runpath that includes /opt/SUNWspro/lib. In that directory in Sun Studio Express is a symbolic link that points to ../prod/usr/lib/libCstd.so.1, the library with version SUNW_1.3.2.
If you try this:
% /opt/SUNWspro/bin/CC hello.cc
% ldd a.out
you should see, among other things,
libCrun.so.1 => /opt/SUNWspro/lib/libCstd.so.1
(Depending on the OS version, you might see
libCrun.so.1 => /opt/SUNWspro/prod/usr/lib/libCstd.so.1 instead.)
But if ldd can't resolve the library, you probably have a corrupted Sun Studio Express installation. In that case, uninstall it, and reinstall from a fresh download.
If you run the program on a different computer where Sun Studio Express is not installed, the loader won't be able to find the right library version, and you will get "not found" results. I addressed this issue in another thread:
http://forums.sun.com/thread.jspa?threadID=5340163

Weblogic 8.1 startup with debug options and struts

I'm trying to startup weblogic 8.1 with the set debug=-Xdebug -Xnoagent -Djava.compiler=NONE
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=7021
option...it will not start up because of something in my .war file however it
does start up fine without the debug settings.
Attached is my war file...
[calendar.war]

The procedure is the same for Oracle database and MySQL. Except the driver class and connection url are different.
Please refer
http://weblogic.sys-con.com/node/43045

Looking for JDK binary compiled with debug info

For some reason JTree.startEditingAtPath() is not doing what I expect, and I'd like to step through the JDK code to see what's going on. Back with Java 5 there were debug builds of the JDK that would let me do this. I've been searching, but cannot find the equivalent for Java 6. Are there still debug binaries out there I can grab (and not have to compile the JDK myself)?

JDK is open source. Just get the source and step through it in your debugger.

Compiling with gcc options

Hi,
I am trying to convert a standalone 'C' library code consisting of ~ 100 h files + 200 c files into 'swc' and run it.
The starting point is a c file called jaz.c.
If I compile using command --> gcc jaz.c -O3 -Wall -swc -o jaz.swc, the swc file which is generated is very small size of 141 kb, and the application does not run.
So I decided to change the strategy. I used the following command first to create '.o' files -->
gcc -I. xfname.c                             //'xfname.c' gets converted to 'xfname.o'
-g -c                                             //various compiler options starts
-DW_NOTACC
-DSSA_CPU_X86_64=1
-DSSA_CPU_LITTLEENDIAN=1
-DSSA_CPU_64BIT_LONG=1
-DSSA_CPU_64BIT_PTR=1
-DSSA_OS_UNIX=1
-DSSA_OS_LINUX_ANY=1
-DSSA_OS_UNIX_LAX=1
-D_XOPEN_SOURCE=500
-D_BSD_SOURCE
-D_SVID_SOURCE
-DEJSAS=1
-DFMTDLL_COMPILE=1
-IC:/FormatDocs/Standalone/TKLAX/h       //Path to various 'h' files/
-IC:/FormatDocs/Standalone/TKPOS/h       // -- " " ---
-IC:/FormatDocs/Standalone/TKPKT/h
-IC:/FormatDocs/Standalone/LAX/h
-IC:/FormatDocs/Standalone/A64/h
-IC:/FormatDocs/Standalone/UNX/h
After running the command I get ~ 200 .o file.
Then I used the command
gcc -I. jaz.c
xfload.o
xfname.o
--                                    //All 200 '.o' files included here
-O3 -Wall -swc -o jaz.swc
By this strategy the compiler generates a huge swc file of ~ 515 kb.
But when I run this application the Flash AS error occours
TypeError: Error #1006: value is not a function.
at cmodule.jaz::FSM_format/work()[1344.achacks.as:68077]
at <anonymous>()[1344.achacks.as:3341]
at <anonymous>()[1344.achacks.as:3902]
I wanted to ask 2 questions.
- Is this way of 2 stage gcc compiling (1st gcc creates .o file, and next gcc creates swc) correct.
- What is the meaning of this run time error "value is not a function."
Thanks,
-Yogen

Alright that did work for what I intended it to do - i.e. have gcc and make available in /usr/bin and functionning correctly. Now Xcode in itself however ... crashes everytime upon opening. Not that I need it now, but I certainly will someday - and not in that long a time, in all probability. It says it could not load the iPhone emulator plugin - and it is just the last of many errors, it says. Check Xcode's crash details out here. Thanks a lot already though !

Compiling with debug and runtime performance degradation

Just a quick question: Does including debug information in class files degrade runtime performance in any way?
Thanks!

Quick answer: it depends on what your application does.
Mostly, it shouldn't matter but you should always profile and time your
application to find the truth.

"no symbolic information for "main" compile with -g option

Hi I get the above message, and I'm sure that my make file specifies -g option. Does any one know what might be happening here?

Hi I get the above message, and I'm sure that my make file specifies -g option. Does any one know what might be happening here?

Calling VI through VI server with Debug Option

Hi All,
I am building application in which I have my own operator Interface (Application.exe(source code is in VI Server. I) which is a exe built using LabVIEW in which i am basically calling another VI(Test call)through VI server concept. When run the operator interface i want the Test call to open in debugging mode(Breakpoint, Probe etc).How to run Calling VI from Development Mode can anybody have suggestions.
Please find the source code and exe.
Testcall.vi is calling VI.
VI server.vi is operator Interface.
Application.exe in build folder is the exe.
Regards,
Satya
Attachments:
VIserver.zip ‏133 KB

I'm sure there is a better way to do this, but here is what I do...
For the VI that I am calling, I place a breakpoint at the start of its code, save it, and close it. Then I run the VI that calls that VI. When the breakpoint is hit the called VI's block diagram will pop up and it will be paused.
Does that help?

Cannot compile code with debug symbols

I have a source code file that will not compile with debug symbols. I get an assertion failed in file ../src/regman/regman_local.cc at line 5224. The compile command and output are below.
/opt/SUNWspro/bin/cc -g -xarch=v9b -xopenmp=noopt -xc99=all -c -o output/spirecon.o spirecon.c
cg: assertion failed in file ../src/regman/regman_local.cc at line 5224
cg: Out of range
cg: 1 errors
cc: cg failed for spirecon.c
However without the debug options and using the default -fast switch, i.e.
/opt/SUNWspro/bin/cc -fast -xarch=v9b -xopenmp=noopt -xc99=all -c -o output/spirecon.o spirecon.c
it compiles without any problems.
I was hoping someone might have a suggestion as to how what might cause this type of error.

I have been told this is bugid: 4420630
It only happens when you try to use the optimizing
backend code generator without any optimization.
(That's what -xopenmp=noopt does)
If you add an -xO1 flag the assertion should go away, but you
will also lose some (but not all) of your debuggability.
--chris

Compiling with debug option

Similar Messages

Maybe you are looking for