Sun Studio code hangs at fork, GCC code runs fine

I am encountering a strange problem where code complied with GCC runs fine, but the same code compiled with Sun Studio 12 compiler hangs at a fork call after an initial set of fork calls.
I'd appreciate your help in solving this.
The code was originally written for GCC, I started using the Sun Studio with a view to using Sun's thread analyzer. I made a couple of changes which I think are inoccuous:
(a) added #ifdef __SUNPRO_CC char * __FUNCTION__ = "name"; #endif
(b) one more #ifdef around one call to ctime_r because the g++ include expects 2 parameters while Sun Studio 12 expects 3 parameters.
The g++ is compiled on a Solaris 9 (1 x sparcv9) using GCC 3.3.3
while the Sun Studio 12 is on a Solaris 10 ( 4 x sparcv9).
Both runs were on the same Solaris 10 machine which has the compiler.
The program is a multi instance socket listener, the main program binds to a socket, then forks off a set of processes which accept connections, those children later fork off other client applications based on the connection data; after those clients exit, the children continue accepting etc. The main program only monitors the child processes, records their status and starts if any of those die.
This is working as expected when compiled with g++.
The exact same code (note the two sets of #ifdefs above) when compiled with Sun PRO CC alway hangs at the second set of fork. That is, it goes through the first set of forks fine, then when a connection is established, it reads the data but hangs right at the fork call.
The application code at this point is:
char * p = pathfind( getenv("PATH"), progname );
if ( !p ) {  printError(); return false; }
pid = fork();
The truss for the Sun Studio code shows
23914: access("/usr/bin/progname", X_OK) = Err#2 ENOENT
23914: access("/usr/you/bin/progname", X_OK) = 0
23914: lwp_park(0x0000000, 0) (sleeping)
while the truss for the g++ code shows
23986: access("/usr/bin/progname", X_OK) = Err#2 ENOENT
23986: access("/usr/you/bin/progname", X_OK) = 0
23996: fork1() = 24005
What am I doing wrong?
Thanks and best regards

If I understand correctly, you are compiling with gcc on Solaris 9, and with Sun Studio on Solaris 10. Since the OS is different, you might be running into OS issues and not compiler issues. What happens if you build with the same gcc version on the Solaris 10 system where you see the problem?
By "OS issues", I mean
1. The program uses unstable or undocumented OS interfaces, or
2. A bug that is new in Solaris 10.
A bug was identified in Solaris 10 that could cause forks to hang. It showed up in the libpkcs11 library as used by the JVM. I don't know whether it showed up elsewhere.
This bug was fixed in Solaris 10u2. If you are using an earlier version of Solaris 10, you could try upgrading.

Similar Messages

  • Sun Studio 12 CC compiler and gcc libraries

    Hi
    We are working on a porting project, Linux to Solaris. The software uses lots ot third party libraries. These libraries are compiled on Linux using gcc. They do not endorse Sun's CC compiler.
    Our project plans to use CC instead. Is it okay to build our software with CC (and fix all the portability issues we may have) and finally link it with all the third party libs created with gcc ? Is such kind of arrangement workable?
    Any advice would be really helpful.
    Thank you,
    Manish.

    Thank you for reporting the problem! I've submitted CR 6642662. It should be visible on web in a day or so.
    Boris

  • Sun Studio cc includes unused static inline functions in object file

    While trying to compile some code originally compiled with GCC I run into a linking problem. My problem seems to be caused by that GCC does not include unused static inline functions in the object files while cc does. The following simple example can be used for illustrating this:
    void foo();
    static inline void bar()
      foo();
    int main()
    }This program compiles and links without any problems using GCC and Sun Studio 12 CC (the C++ compiler) but fails to link using Sun Studio 12 cc:
    khepri%> cc staticinline.c
    Undefined first referenced
    symbol in file
    foo staticinline.o
    ld: fatal: Symbol referencing errors. No output written to a.out
    It is probably fine of cc to include foo() in the object file (although not necessary?). My questions are:
    1. Are there any reasons for why cc includes unused static inline functions in the object file while CC does not?
    2. Are there any ways or options to tell cc to not include unused static inline functions in the object file?
    In the example above this is easy to fix by just removing or #ifdef away the code but the original code where I have this problem is not maintained by me and the static inline functions are in header files that get included in multiple C files and in some of these the functions are used.
    Thanks,
    Olav

    olavsa wrote:
    1. Are there any reasons for why cc includes unused static inline functions in the object file while CC does not?
    2. Are there any ways or options to tell cc to not include unused static inline functions in the object file?Removing dead code is an optimization, so you need at least -xO1 for that.

  • Compiling MySQL 5.1.26-rc with Sun Studio Express on Linux?

    I managed to compile MySQL 5.1.26-rc with Sun Studio Express on Linux (OpenSuse 10.2 on x64), but I get unexpected crashes every time a connection thread exits:
    (gdb) where
    #0  0x00002b2ce0649535 in raise () from /lib64/libc.so.6
    #1  0x00002b2ce064a990 in abort () from /lib64/libc.so.6
    #2  0x00002b2cdf949795 in __pthread_unwind () from /lib64/libpthread.so.0
    #3  0x00002b2cdf944425 in pthread_exit () from /lib64/libpthread.so.0
    #4  0x00000000005048b2 in one_thread_per_connection_end (thd=0x16d88f0, put_in_cache=false)
    at /home/mysql/debug/sql//mysqld.cc:1893
    #5  0x0000000000513b75 in handle_one_connection (arg=0x16d88f0) at /home/mysql/mysql-5.1.26-rc/sql//sql_connect.cc:1122
    #6  0x00002b2cdf94309e in start_thread () from /lib64/libpthread.so.0
    #7  0x00002b2ce06da4cd in clone () from /lib64/libc.so.6
    #8  0x0000000000000000 in ?? ()If I compile with gcc using e.g. BUILD/compile-amd64-debug-max, I have no issue! But I want to use Sun Studio in order to be consistent with the Solaris version, and also because Sun Studio is likely to produce better code.
    Here is the compilation script, it downloads and extracts the source tree and builds it (it assumes Sun Studio Express is installed in /opt/sun):
    #!/bin/bash
    export PATH=/opt/sun/sunstudioceres/bin:$PATH
    wget -q http://mir2.ovh.net/ftp.mysql.com/Downloads/MySQL-5.1/mysql-5.1.26-rc.tar.gz
    tar xpf mysql-5.1.26-rc.tar.gz
    cd mysql-5.1.26-rc
    # Explicitly specify libs to avoid linking with the STL.
    export LIBS="-xnolib -lCrun -lm -lc -lrt"
    autoreconf --force --install > autoreconf.log 2>&1
    export MY_FLAGS="-g -mt -xtarget=generic -m64"
    CC=cc CXX=CC CFLAGS=$MY_FLAGS CXXFLAGS=$MY_FLAGS ./configure --with-big-tables --without-embedded-server --disable-shared --with-pthread --with-ssl -with-plugins=max > configure.log 2>&1
    gmake -j > build.log 2>&1Any idea about what is going wrong?
    Thanks.

    Possibly the actual CC (or cc) command lines are not correct. The proper way to say not to link libCstd is the command-line option -library=no%Cstd. Then you don't need to add the default system libraries like -lc to the command line.
    Can you show the actual CC command lines that are generated by the makefile? They should be in the compilation log. I'd also like to see the command line(s) used to create dynamic libraries, if any, and the final executable.

  • Welcome to the Sun Studio General Discussion!

    Ask questions or seek answers to topics that do not fit other Sun Studio forums, such as installation, upgrading to recent Studio versions, IDE wizards, and documentation.
    In addition, visit the Sun Studio developer site for technical articles, code samples, knowledge base and more:
        http://developers.sun.com/sunstudio
    Finally, make sure you have the latest version of Sun Studio as well as appropriate patches:
        http://developers.sun.com/prodtech/cc/downloads/index.html

    Here is content of my .cshrc file:
    # @(#)cshrc 1.11 89/11/29 SMII'm sorry, it seems like I wasn't clear about what I meant.
    The command "sunstudio" is itself a shellscript. It isn't a binary executable. In Sun Studio 10 it is a bash script. It's first line is
    #!/bin/bash
    This means that when it is passed to the exec system call, the kernel searches for /bin/bash, and runs bash with its input connected to the script. If you don't have bash on your system, you will get the message you described (although there could be other reasons for getting that message).
    You need to check whether /bin/bash exists on your system, and if it doesn't, install the appropriate package from the Solaris companion software CD. I believe the package is SUNWbash.
    --Terry.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

  • Legacy versions of Sun Studio

    In my work I maintain a legacy version of my company's product, which is compiled and built using Sun Studio 10.
    This hasn't been a problem until recently when we purchased a new Sun machine which came pre-installed with version 12, and I just discovered that Sun recently ceased support for version 10.
    So it seems I am not allowed to purchase version 10 to support my product.
    Can someone advise me on the options? Are there any options? If not, it means I may not be able to support the customers I have running this version of my product...
    Thanks
    Sean

    Indeed, Sun Studio 10 is EOL (see http://developers.sun.com/sunstudio/support/matrix/index.jsp). But since you already have it, I suppose you only need it on another machine, right?
    Of course, no new patches for Sun Studio 10 are produced so should you run into a problem, there is no option other than upgrade or implement a workaround.
    What exactly is the reason for building your project with Sun Studio 10? If you absolutely must support aging Solaris 8, you still can upgrade to Sun Studio 11 at least (however, it won't help you a lot, its EOL date is approaching as well). And if you don't have to stay on Solaris 8, you can try latest Sun Studio 12 update 1, which is free and can be downloaded here: http://developers.sun.com/sunstudio/downloads/thankyou.jsp

  • Installed Sun studio 12.2. ran 'discover' command on C++ code.Gives warning

    Hi,
    I installed Sun studio 12.2. I compiled C++ code with C++ 5.11 compiler, and ran discover command as shown below:
    > #CC -g -O2 test.cpp
    > #discover -w - a.out
    > discover (warning): a.out will be analyzed in lite mode because it has no annotations. See discover documentation for compiler flag/OS recommendations
    I get the discover warning. After runnig discover command, I executed ./a.out. On cosole, only memory leaks will be displayed and no other error.
    Any reason why discover gives warning??????????????????
    Edited by: Archit on Apr 5, 2011 11:09 PM
    Edited by: Archit on Apr 5, 2011 11:10 PM
    Edited by: Archit on Apr 5, 2011 11:10 PM
    Edited by: Archit on Apr 5, 2011 11:13 PM

    Hi,
    What a woderful fix you have provided !!!!!!!!!!
    It really works.
    I tried running on Solaris 10 update 8. discover tool runs properly. Where as , the tool runs in lite mode on Solaris update 4.
    If possible , can you pint me to some links where I can this kind of info.?
    Thank you very much.

  • Code generation bug in Sun Studio 12

    Hi,
    The following program prints `Failure' when compiled with -xO4 where nothing should be printed (when compiled with no optimization or -xO2). It looks to me that the first comparison `buggy_routine' against 0x80 is returning True where it should return False.
    #include <stdlib.h>
    #include <stdio.h>
    typedef unsigned long long int      EIF_NATURAL_64;
    typedef unsigned char   EIF_BOOLEAN;
    typedef int EIF_INTEGER_32;
    typedef char * EIF_REFERENCE;
    char s[] = "9223372036854775808";
    void buggy_routine (EIF_REFERENCE Current, EIF_NATURAL_64 arg1)
        EIF_NATURAL_64 tu8_1;
        tu8_1 = (EIF_NATURAL_64) ((EIF_INTEGER_32) 128L);
        if ((EIF_BOOLEAN) (arg1 <= tu8_1)) {
        } else {
            if ((EIF_BOOLEAN) (arg1 <= ((EIF_NATURAL_64)  9223372036854775808ull ))) {
            } else {
                  printf("Failure\n");
    int main (int argc, char ** argv, char **envp ) {
        EIF_NATURAL_64 loc2 = (EIF_NATURAL_64) 0;
        loc2 = (EIF_NATURAL_64) atoll(s);
        buggy_routine ("s", loc2);
    }To reproduce:
    cc -xO4 bug.c -o bug ; ./bug
    It fails on both 32 and 64-bit code generation for x86. I haven't tried on Sparc as I need to install Sun Studio 12. Is this a known issue? Is there an easy workaround?
    I tried with Sun Studio 11 and it worked just fine there.
    Regards,
    Manu
    PS: I've tried with both version (the first is the one from the default installation) and the second after I noticed there were some patches available:
    cc: Sun C 5.9 SunOS_i386 Patch 124868-01 2007/07/12
    cc: Sun C 5.9 SunOS_i386 Patch 124868-02 2007/11/27

    An issue filed at bugs.sun.com does not go directly into the bug database. It is evaluated, and if it turns out the report is actually a bug not previously reported, goes into the database. You get a notification and chance to reply after the report is evaluated.
    In this case, I picked up your report myself, and filed the bug. The bug ID is 6654314, and will be visible at bugs.sun.com in a day or two.

  • Tcov Code Coverage Libraries missing from Sun Studio 12!!!

    Hi,
    When I try to collect coverage statistics using the -xprofile=tcov I get the following message
    f90     -xprofile=tcov -w0 -C  -c ./intfaces.f90 -o ./scovintfaces.o
    f90     -xprofile=tcov -w0 -C  -c ./gcovsrc.f90 -o ./scovsrc.o
    f90     -xprofile=tcov -w0 -C  -c ./gcovdrv.f90 -o ./scovdrv.o
    f90      -xprofile=tcov -w0 -C  -o ./five82scov.exec ./scovdrv.o ./scovsrc.o /usr/lib/libg2c.so.0 
    f90: Cannot find /opt/sun/sunstudio12/prod/lib/bb_link.oThis file does not seem to be within the packages provided in sun studio 12!!! (linux/x86 editon). I then decided to get the latest patches and now I get the following message
    f90     -xprofile=tcov -w0 -C  -c ./intfaces.f90 -o ./scovintfaces.o
    /opt/sun/sunstudio12/prod/bin/f90comp: error while loading shared libraries: libyabe.so: cannot open shared object file: No such file or directoryThis file is also nowhere to be found!!! Have the sun developers decided to leave out crucial libraries?!?
    Regards

    This is not very nice from the compiler, but at least it is documented here:
    http://developers.sun.com/sunstudio/documentation/ss12/mr/READMEs/fortran_95.html#limitations
    Quote:
    The -xprofile=collect and -xprofile=tcov options should not be used when building shared libraries on Linux.

  • Studio 12: C compiler generates bad code with -m64 -KPIC -xO2

    Hello,
    after upgrading my Solaris 10/x64 machine from Studio 11 to Studio 12 some problems were fixed, but others came up; like this one:
    I have a code snippet that obviously causes the C compiler to generate wrong code if compiled with options -m64 -KPIC -xO2. If any of these options are missing, it runs fine. Here's the example code:
    #include <stdio.h>
    #include <strings.h>
    static int do_something() { return 0; }
    static int foo() {
        fprintf(stderr, "\n!! BUG: BAD CODE! unexpected function call foo()!\n\n");
        return 222;
    static int bar() {
        fprintf(stdout, "\nOK: bar() called\n\n");
        return 0;
    static const struct {
        const char* name;
        int (*func)();
        int flag;
    } tab[] = {
        { "foo",  &foo,  0 },
        { "bar",  &bar,  0 },
        { 0, 0, 0 }
    int main(int argc, const char** argv) {
        int i;
        for (i=0; tab.name; i++) {
    if( strcmp(tab[i].name, "bar") == 0 ) {
    if(tab[i].flag) {   /* not reached */
    if(!do_something()) {
    return 2;
    return (*tab[i].func)();
    return 1; /* not reached */
    Many lines seem to be bogus, but they are actually needed to reproduce the problem.
    This is what happens:# cc -m64 -KPIC -xO2 bug.c && ./a.out ; echo $?
    !! BUG: BAD CODE! unexpected function call foo()!
    222
    If I compile with debugging information (-g), I get expected behavior, which is:# cc -m64 -KPIC -g bug.c && ./a.out ; echo $?
    OK: bar() called
    0
    While creating the test case I've also seen SIGSEGV at runtime in the bug case - which is probably due to a wrong calculated function address for jmp (just guessing).
    Does anyone know if this is a known bug?
    Any help is appreciated.
    The rest of this posting is information about my system and Studio 12 patch level:# uname -a
    SunOS v20 5.10 Generic_137112-08 i86pc i386 i86pc
    # /usr/SUNWspro/bin/version
    Machine hardware: i86pc
    OS version: 5.10
    Processor type: i386
    Hardware: i86pc
    The following components are installed on your system:
    Sun Studio 12
    Sun Studio 12 C Compiler
    Sun Studio 12 C++ Compiler
    Sun Studio 12 Tools.h++ 7.1
    Sun Studio 12 C++ Standard 64-bit Class Library
    Sun Studio 12 Garbage Collector
    Sun Studio 12 Fortran 95
    Sun Studio 12 Debugging Tools (including dbx)
    Sun Studio 12 IDE
    Sun Studio 12 Debugger GUI
    Sun Studio 12 Performance Analyzer (including collect, ...)
    Sun Studio 12 X-Designer
    Sun Studio 12 VIM editor
    Sun Studio 12 XEmacs editor
    Sun Studio 12 Performance Library
    Sun Studio 12 LockLint
    Sun Studio 12 Building Software (including dmake)
    Sun Studio 12 Documentation Set
    Sun Studio 12 /usr symbolic links and GNOME menu item
    version of "/usr/SUNWspro/bin/../prod/bin/../../bin/cc": Sun C 5.9 SunOS_i386 Patch 124868-07 2008/10/07
    version of "/usr/SUNWspro/bin/../prod/bin/../../bin/CC": Sun C++ 5.9 SunOS_i386 Patch 124864-08 2008/10/16
    version of "/usr/SUNWspro/bin/../prod/bin/../../bin/f90": Sun Fortran 95 8.3 SunOS_i386 Patch 127002-04 2008/04/16
    version of "/usr/SUNWspro/bin/../prod/bin/../../bin/dbx": Sun Dbx Debugger 7.6 SunOS_i386 Patch 124873-06 2008/08/20
    version of "/usr/SUNWspro/bin/../prod/bin/../../bin/analyzer": Sun Analyzer 7.6 SunOS_i386 Patch 126996-04 2008/09/03
    version of "/usr/SUNWspro/bin/../prod/bin/../../bin/dmake": Sun Distributed Make 7.8 SunOS_i386 Patch 126504-01 2007/07/19

    I'm watching Bug ID: [6774287|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6774287] for quite a while and it seems to be fixed some time ago (State: 8-Fix Available, bug). Does anybody know if the fix made it in some officially available SunStudio 12 C compiler (backend) patch already? I'm using this SS12 patch-level meanwhile:
    # /usr/SUNWspro/bin/version
    version of "/usr/SUNWspro/bin/../prod/bin/../../bin/cc": Sun C 5.9 SunOS_i386 Patch 124868-08 2008/11/25
    version of "/usr/SUNWspro/bin/../prod/bin/../../bin/CC": Sun C++ 5.9 SunOS_i386 Patch 124864-09 2008/12/16
    version of "/usr/SUNWspro/bin/../prod/bin/../../bin/f90": Sun Fortran 95 8.3 SunOS_i386 Patch 127002-05 2008/10/21
    version of "/usr/SUNWspro/bin/../prod/bin/../../bin/dbx": Sun Dbx Debugger 7.6 SunOS_i386 Patch 124873-06 2008/08/20
    version of "/usr/SUNWspro/bin/../prod/bin/../../bin/analyzer": Sun Analyzer 7.6 SunOS_i386 Patch 126996-04 2008/09/03
    version of "/usr/SUNWspro/bin/../prod/bin/../../bin/dmake": Sun Distributed Make 7.8 SunOS_i386 Patch 126504-01 2007/07/19

  • Code runs fine in debug mode but hangs when compiled in release mode

    I am struggling with the following problem. I have code which runs fine when it is executed in debug mode. However, when I compile it in release mode and run the executable, the code freezes and does not work. The code acquires images from a Hamamatsu camera. In the debug mode I am able to continuously acquire images. However, in the release version, the code hangs after acquiring the first image.
    I am using LabWindows/CVI version 7.
    I would greatly appreciate if I can get any help/suggestions in resolving this problem?
    Thanks!
    Regards,
    Sripad
    Solved!
    Go to Solution.

    Sripad:
    If you search this forum for "debug release crash" or "release version crash" or similar phrases, you'll find that this is a pretty common question.  Look through the other posts you find here to see if anything is applicable to you.
    The debug version does some things like padding variables so you can sometimes overrun your declared variable space without overwriting the next variable.  In the release, the variables are packed, so if you overrun one, you are overwriting another.  Just one possible difference.
    You can do some things in your release code to see where things get lost, like (temporarily using printf statements after multiple statements at the start and end of your loop to try to identify that failing line of code.
    Look through other threads to find other ideas.

  • Sun C++ versus GNU C++ on integer code.

    Hello,
    I've been always wondering why so much people praise Sun C++ for generating highly optimized code and why I'm never able to get my project working faster when being compiled by Sun C++ in comparison with GNU C++. I'm testing MICO and nbench2 and it looks like Sun C++ generates slower integer code while faster floating point code. Is there any way how to make Sun C++ generate faster integer code? Please see [http://developmentonsolaris.wordpress.com/2010/03/06/sun-c-versus-gnu-c-never-ending-wonder-just-resolved/] for more information.
    Thanks,
    Karel

    Try some of these options, IME they are probably most likely to help:
    -fast -xprefetch -xprefetch_level=3 -xprefetch_auto_type=indirect_array_access -xipo=2 -xdepend=yesSome others that could help, depending on your code:
    -xunroll
    -xpagesize (and all its subtypes)
    -xalias_level
    You'd need to experiment to find out.
    Of interest is that some algorithms run faster with inlining and prefetching disabled. Algorithms that are extremely register-intensive can sometimes run faster with no inlining or prefetching because both those optimizations increase the use of registers for any source code. FFTW is one of these - it can run 30 or 40% faster with inlining and prefetching disabled.
    Reference:
    [http://docs.sun.com/app/docs/doc/820-7599/bkana?a=view|http://docs.sun.com/app/docs/doc/820-7599/bkana?a=view]

  • GCC and Sun Studio 12 compatibility ?

    What is the level of compatibility between g++ for SPARC systems and the Sun Studio C++ compilers for SPARC ?
    If I build a shared library using g++ for SPARC is it safe for objects built with the Sun C++ compilers to use these shared libraries ?

    They are completely incompatible, there is no way you can mix them.

  • Sun Studio Debugging problem

    Hello
    I need help configuring the Sun studio debugger to work in fedora 8. The project is loaded from a make file, compiles fine, and runs fine. However, I can not place break points, and when I start the visual debugger, it gives a message box titled progress, and hangs on saying: starting debugger: /lib/libc.so.6
    Running from the command line gives me:
    $dbx <my program>
    For information about new features see `help changes'
    To remove this message, put `dbxenv suppress_startup_message 7.6' in your .dbxrc
    Reading <my program>
    Reading ld-linux.so.2
    Reading libm.so.6
    Reading libmpich.so.1.1
    Reading libpthread.so.0
    Reading librt.so.1
    Reading libc.so.6
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: warning: unknown location expression code (0xe0)
    dbx: panic: "ThreadAgent::setup_helper"(): Assertion (ta_td_agent) failed - "thread.cc":2674
    I have another problem in debugging an mpi problem in another installation of Sun Studio on Solaris 10 on a Sun machine. The visual debugger is working fine there, however, I need to debug with mpirun
    to decide the number of processors, because by default it loads the application on one processor. Iwill need to do this as well later on the linux machine I am using now, which doesn't even start the debugger on a sequential code so far.
    I appreciate your help a lot.
    Thank you very much in advance.
    Manal

    mhelal wrote:
    Hi
    Thank you for your reply. you said 2 problems,Yes, basically I meant these two:
    1. dbx: warning: unknown location expression code (0xe0)
    2. dbx: panic: "ThreadAgent::setup_helper"(): Assertion (ta_td_agent) failed - "thread.cc":2674
    First one should be fixed in dbx itself, but the second looks like an incompatibility between Fedora's libc and dbx; unless distros in "supported" list upgrade to the same version of libc, dbx can't be changed to match it.
    In other words, I'm sorry to say that you will probably not succeed in using dbx on Fedora 8 for the time being.

  • Building NCAR Graphics 5.2.1 on Solaris 10 x86u9 under Sun Studio 10 (2005)

    Hello,
    I've got the following error when compiling ncar program with Sun
    cc and f90 and /usr/ccs/bin/ld.
    cc -ansi -O -I/usr/openwin/include -I/usr/include/X11 -DSYSV -
    D_POSIX_SOURCE -D_XOPEN_SOURCE -DByteSwapped -Di386 -DNeedFuncProto -
    c cl.c
    cc: Warning: illegal option -nsi
    cc: -a conflicts with -dy.
    *** Error code 1
    make: Fatal error: Command failed for target `cl.o'
    After that i've changed the config/SolarisPC file and tried a build with gcc 3.4.3 and f90 but I got
    ld fatal: library -lc not found.
    I have an old box from 2001 which was under HCL of Solaris 8 x86.
    The people at NCAR did not update their configuration files for Solaris 10 x86. The SolarisPC file is old and is using by default g77 as the fortran compiler. Could I mix gcc with f90 ? Which linker should I use in that case?
    /usr/ccs/bin/ld or /usr/ucb/ld?

    Please refer to the C Users Guide for details of cc command line options. All manuals for Sun Studio 12u1 are listed here:
    http://download.oracle.com/docs/cd/E19205-01/index.html
    There is no -ansi option in Sun/Oracle C, nor has there ever been. The compiler attempts to interpret it as -a followed by some other letters, which is why you get a complaint about -a. Remove the option.
    Depending on what you expect from the -ansi option, either the default compiler behavior or the -Xc option should work. I suggest trying the default behavior (no -X option). Refer to the manual for details.
    Always use the /usr/ccs/bin/ld linker, but you normally should not use the ld linker directly. If you mixing C and Fortran, use the f90 driver to do the linking; it knows what Fortran libraries need to be linked, depending on command line option. When linking a program using only C, use the cc driver to link. Some C command-line options require linking special system files; the cc and f90 drivers know the rules.
    To mix Fortran with C, refer to the Fortran Users Guide. I recommend using the Studio C compiler when mixing code, not gcc. The requirements of gcc are not known to the f90 driver, but it does know the requirements of Studio C.
    The schema for a mixed Fortran and C program is something like this:
    cc -c f1.c f2.c <other options>
    f90 -c f3.f90 f4.f90 <other options>
    f90 -o myprog f1.o f2.0 f3.0 f4.0 <other options>

Maybe you are looking for

  • How to find the user who has changed a field in a table

    Hello     Someone has changed a field  cost center in my table so i need to find the user who hav changed it.Can anyone tel me how to find it. Regards

  • Problem with email hang

    hello,when i open the apple mail client it hangs after a few seconds the a spinng beach ball appears ,i force it to quit it wants to send a report to apple ,i click on the middle box to copy the report and then post so the some kind person could look

  • Terminated with error: REP-1924: Cannot locate the font file 'Arialbd.ttf'

    hi all i am using Application server 10g R2 while running report i am getting the following error Terminated with error: REP-1924: Cannot locate the font file 'Arialbd.ttf' i configured the Reports_Path with C:\windows\fonts if anyone faced the same

  • Looking for a theme that looks like the default theme.

    I'm looking for a theme that looks exactly like the default theme, but that doesn't use the colours of my gnome theme. Right now I'm using a dark gnome theme that looks great, but looks horrible with firefox. Anybody got any suggestions? Alternativel

  • Forms 2.1

    Hi... When I run a form with an LOV, I get a message box that asks for "Do you want to save the changes you have made? Yes No Cancel." I always say "No" because I am not sure if it is trying to write to the database. I checked all of the properties o