This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: SIGABRT crashing a process

From: Jonathan Wakely <jwakely dot gcc at gmail dot com>
To: dewasi <piyush_tilloo at yahoo dot co dot in>
Cc: libstdc++ at gcc dot gnu dot org
Date: Mon, 24 Jan 2011 08:53:33 +0000
Subject: Re: SIGABRT crashing a process
References: <30707259.post@talk.nabble.com> <AANLkTikkt-hRePWHE5SRyUy8FteWhuNYwdnV4_-rOvC5@mail.gmail.com> <30746095.post@talk.nabble.com>

On 24 January 2011 06:38, dewasi wrote:
>
> Hi Johnathan,
> ? ? ? ? ? ? ? ? ? Thanks for the comments,Sending the stack in a bit more
> detail , i am a bit new to unix/linux, would appreciate any help or pointer
> from your side.

The stack trace below appears to have debugging info present already
(maybe you'd edited the first one you sent?)

It indicates a bug in your program or one of the libraries you're
using, it's not a problem with libstdc++ so it's not relevant on this
mailing list.  You need to try to isolate the bug, maybe using
valgrind, then produce a small testcase that reproduces it and either
fix your program or report a bug to the supplier of a library.

Jonathan

References:
- SIGABRT crashing a process
  - From: dewasi
- Re: SIGABRT crashing a process
  - From: Jonathan Wakely
- Re: SIGABRT crashing a process
  - From: dewasi

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]