Re: 64-bit c++ application crashing on solaris
- From: Giorgos Keramidas <keramida@xxxxxxxxxxxxxxx>
- Date: Mon, 31 Mar 2008 11:59:54 +0300
On Sun, 30 Mar 2008 23:11:53 -0700 (PDT), Sumir <sumirmehta@xxxxxxxxx> wrote:
I ran a truss on the application to have a trace. It resulted into
this ...
lwp_sema_post(0xFFFFFFFF7D003D60) = 0
lwp_mutex_lock(0xFFFFFFFF7E72B068) = 0
read(39, " 3 e c 0 a 8 f 1 c 7 d 0".., 512) = 512
lwp_mutex_wakeup(0xFFFFFFFF7E72B068) = 0
time() = 1205757131
lwp_mutex_lock(0xFFFFFFFF7E72B068) = 0
Incurred fault #6, FLTBOUNDS %pc = 0xFFFFFFFF7E449BBC
siginfo: SIGSEGV SEGV_MAPERR addr=0x0FAE0350
Received signal #11, SIGSEGV [default]
siginfo: SIGSEGV SEGV_MAPERR addr=0x0FAE0350
*** process killed ***
Seems there is some memory access violation. But the thing is, this
same application compiled in 32-bit mode, run on the same environment
(same machine) fares well. So if it were something to do within the
code, in way of accessing memory wrongly, it should have surfaced in
the 32-bit version as well.
Not necessarily. There are many programs which implicitly assume that
`int' is large enough to hold a memory address. They tend to work find
in 32-bit mode (because their assumption happens to be true), but fail
randomly in 64-bit mode.
.
- References:
- 64-bit c++ application crashing on solaris
- From: Sumir
- Re: 64-bit c++ application crashing on solaris
- From: Paul Pluzhnikov
- Re: 64-bit c++ application crashing on solaris
- From: Sumir
- 64-bit c++ application crashing on solaris
- Prev by Date: Re: 64-bit c++ application crashing on solaris
- Next by Date: Re: Can a file be deleted even if it is in use.
- Previous by thread: Re: 64-bit c++ application crashing on solaris
- Next by thread: Re: 64-bit c++ application crashing on solaris
- Index(es):
Relevant Pages
|
