Hi,
I am not familiar with HPUX's development environment, but
I experience quite a large amount of crashes with STL to ask me
if I am using the correct (bug free) implementation.
So, I suggest the following:
1. Make a simple example using std::string and see if the same functions work 2. Use the latest STLPort headers (sorry, I don't know how well they compile on HPUX, but they should work )
3. If nothing works, then there is a problem with the memory allocator.
Try to use another compiler. (i doubt that this is the case)

Let us know how everything worked out and I'll have a look at that code if needed.

Mark Richardson wrote:
I've been trying to upgrade some of our stuff to mico-2.3.12, in hopes that the latest version fixes all of the problems that we're having. However, I can seem to get mico-2.3.12 to compile correctly on HPux 11i. We are using aCC for the compiler, and I think I'm compiling it correctly. micod runs, and I'm able to use imr to interact with the micod. However, when I make a simple stand alone application, it crashes. The stack looks like this...
#0 in pthread_mutex_destroy+0x18() from /usr/lib/libpthread.1
#1 in __thread_mutex_free+0x40 () from /usr/lib/libc.2
#2 in _HPMutexWrapper::~_HPMutexWrapper+0x34 () from /usr/lib/libstd_v2.2
#3 in std::basic_string<char,std::char_traits<char>,std::allocator<char>>::_C_unlink #4 in std::basic_string<char,std::char_traits<char>,std::allocator<char>>::replace ()
#5 in MICOGetOpt::parse() at util.cc: 602
#6 in CORBA::ORB_init() at orb.cc 3317
#7 in setupOrb()
#8 in main()
Any help is appreciated - I've been scratching my head of why the std::string::operator[] is causing this - but I'm at a loss. Thanks,
Mark

*/Karel Gardas <[EMAIL PROTECTED]>/* wrote:

    Date: Fri, 29 Jun 2007 11:03:50 +0200
    From: Karel Gardas <[EMAIL PROTECTED]>
    To: Mark Richardson <[EMAIL PROTECTED]>,
    MICO Devel Mailing List <mico-devel@mico.org>
    Subject: Re: [mico-devel] Mico apps crashing - problem seems to be X11


    Mark,

    it would great if you experience any crashes to obtain a backtrace for
    us. Also the way how did you configured MICO and what exactly platform
    (OS + C++ compiler name and version) do you use might also be important.

    Anyway, I always recommend to try to duplicate any bug in obsolete
    releases with the last release. Perhaps it's already solved?

    Thanks,
    Karel

    Mark Richardson wrote:
     > Hi all, You've all been a great help in the past, so I thought I'd
     > see if yout could help me with this.
     >
     > We've been running HP-Ux 11i with mico 2.3.7 (I'll get to the update
     > in a minute). It's been running great with a couple of exceptions.
     > One particular Gui client crashes, and after debugging I found that
     > mico is crashing on MICO::TCPTransport::write. Specifically, the
     > MICO::GIOPConn::Output which I found to crash when the tail pointer
     > doesn't end up at the head pointer after a write. Other machines
     > never have the tail pointer not equal to the head pointer after a
     > write.
     >
     > This is an odd failure because it doesn't happen on other machines,
     > and it's sporatic on this particular machine. This machine is
     > running X11 and most of the others are running X11 version 1.
     >
     > So I thought I'd upgrade to mico 2.3.11 (I've found mico 2.3.12+ has
     > too many changes to go that far yet). After this, the Gui crashes
     > during an orb->bind call. But I don't think it's the speicific call
     > to bind, because the debugger shows that its after the X11Dispatcher
     > on a callback.
     >
     > Interesting data point is when I ran this gui on other machines it
     > worked with just mico2.3.11 and micocoss2.3.11 lib. While this
     > problem machine also required micox2.3.11 lib.
     >
     > So the question comes down to this - Is there a known issue with X11
     > vs X11 version 1 and event processing when working with mico2.3.7 or
     > mico2.3.11?
     >
     > Thanks for any help/ideas/suggestions in advance, Mark
     >
     >
     > --------------------------------- We won't tell. Get more on shows
     > you hate to love (and love to hate): Yahoo! TV's Guilty Pleasures
     > list.
     >
     >
     >
    ------------------------------------------------------------------------
     >
     >
     > _______________________________________________ Mico-devel mailing
     > list Mico-devel@mico.org
     > http://www.mico.org/mailman/listinfo/mico-devel


-- Karel Gardas [EMAIL PROTECTED]
    ObjectSecurity Ltd. http://www.objectsecurity.com


------------------------------------------------------------------------
Yahoo! oneSearch: Finally, mobile search that gives answers <http://us.rd.yahoo.com/evt=48252/*http://mobile.yahoo.com/mobileweb/onesearch?refer=1ONXIC>, not web links.


------------------------------------------------------------------------

_______________________________________________
Mico-devel mailing list
Mico-devel@mico.org
http://www.mico.org/mailman/listinfo/mico-devel
_______________________________________________
Mico-devel mailing list
Mico-devel@mico.org
http://www.mico.org/mailman/listinfo/mico-devel

Reply via email to