Re: 64-bit c++ application crashing on solaris



Sumir wrote:
On Mar 31, 11:22 am, Ian Collins <ian-n...@xxxxxxxxxxx> wrote:
Sumir wrote:
On Mar 29, 10:14 am, Paul Pluzhnikov <ppluzhnikov-...@xxxxxxxxx>
wrote:
Sumir <sumirme...@xxxxxxxxx> writes:
The application seems to be crashing intermittently for no specific
reason.
Oh, there *is* a reson (or a few).
The very first question you should ask is where exactly is it
crashing? Use debugger to find out.
We think this could probably be due to sufficient memory not available
to the 64-bit application.
You have not presented any reason why you'd think that.
Cheers,
--
In order to understand recursion you must first understand recursion.
Remove /-nsp/ for email.
Hi Paul,
I ran a truss on the application to have a trace. It resulted into
this ...
What do you see in your debugger? If there's a core file, load that.

--
Ian Collins.- Hide quoted text -

- Show quoted text -

*Please* don't quote signatures or that google nonsense.



I did have a couple of core files. Loading them gives the following
stack trace --

Your Date constructor looks to be a prime contender, run the application
under dbx until it crashes and see what it is passing to do_get_date.

I'm guessing you are building with Sun Studio, using the default STL.
If so, try stlport4.

--
Ian Collins.
.



Relevant Pages

  • Re: 64-bit c++ application crashing on solaris
    ... The very first question you should ask is where exactly is it ... Use debugger to find out. ... You have not presented any reason why you'd think that. ... In order to understand recursion you must first understand recursion. ...
    (comp.unix.programmer)
  • Re: 64-bit c++ application crashing on solaris
    ... The very first question you should ask is where exactly is it ... Use debugger to find out. ... You have not presented any reason why you'd think that. ... In order to understand recursion you must first understand recursion. ...
    (comp.unix.programmer)
  • Re: real random
    ... The reason is because there is no way to keep the ... debugger out of a mainstream system -- i.e., ... By not showing the process that generates numbers? ...
    (comp.lang.c)
  • Re: advantages of C
    ... Only if you're using a debugger that doesn't understand about name ... But gdb handles gnu C++ name mangling these days, ... plenty of free ones around, so no reason I can see not to use one... ... You all think I'm paranoid, ...
    (comp.programming)
  • Re: kbdmux vs ATA? (was: ATA related panic during ZFS scrub)
    ... I guess the policy was to not pick up any locks while in the debugger. ... The reason for the second rule should be obvious, but the reason for the first rule is less obvious: it's called during the boot in all kinds of sensitive places as a result of calls to printf, so has to be willing to run under the most sticky of circumstances. ...
    (freebsd-current)