From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Rony Paul <ronypaul77@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: compilation error
Date: Wed, 08 Jun 2011 13:31:00 -0000 [thread overview]
Message-ID: <BANLkTinnzXp7nduGpyZQvSUj8saha3V8ng@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=eSxkE3qCdFZf42pEZHYy0npLE4w@mail.gmail.com>
On 8 June 2011 12:09, Rony Paul wrote:
>
> could you please tell me what type of error is the following code returning?
It looks as though you're dereferencing a null pointer. Find out
which line it segfaults on and add checks to ensure the relevant tree
variable is not null before using it.
next prev parent reply other threads:[~2011-06-08 12:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 12:25 Rony Paul
2011-06-08 13:31 ` Jonathan Wakely [this message]
2011-06-08 13:47 ` Ian Lance Taylor
-- strict thread matches above, loose matches on Subject: below --
2012-08-15 15:43 Configuration Error Jonathan Wakely
2012-08-15 17:49 ` B B
2012-08-15 17:57 ` Jonathan Wakely
2012-08-15 18:03 ` Compilation Error Ron Stubbs
2012-08-15 18:14 ` Marc Glisse
2012-08-15 18:46 ` B B
[not found] ` <CAH6eHdRV5NLCO-+iJw1FHqw+6EV-LSCNkhF-SJ0jZUPtdbwFKQ@mail.gmail.com>
2012-08-15 19:25 ` Jonathan Wakely
2012-08-15 19:36 ` Ron Stubbs
2012-08-16 3:59 ` Marc Glisse
2012-08-16 13:29 ` Ron Stubbs
2012-08-16 15:15 ` Tim Prince
2012-08-16 20:06 ` Marc Glisse
2012-08-17 0:12 ` Ron Stubbs
2012-08-17 7:23 ` Marc Glisse
2012-08-17 8:23 ` Jonathan Wakely
2006-10-07 18:58 compilation error ranjith kumar
2006-10-07 19:36 ` Tim Prince
2005-07-18 4:24 Compilation error Oleg Kotsyurbiy
2005-07-18 5:51 ` Ian Lance Taylor
2005-07-18 7:45 ` Arturas Moskvinas
2000-02-21 10:27 Jose Miguel A.C.Pires
2000-02-21 10:39 ` llewelly
2000-04-01 0:00 ` llewelly
2000-04-01 0:00 ` Jose Miguel A.C.Pires
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BANLkTinnzXp7nduGpyZQvSUj8saha3V8ng@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=ronypaul77@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).