unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jan D." <jan.h.d@swipnet.se>
Cc: emacs-devel@gnu.org
Subject: Re: Problem report #33 RESOLVED
Date: Sun, 14 May 2006 13:31:16 +0200	[thread overview]
Message-ID: <44671504.9010808@swipnet.se> (raw)
In-Reply-To: <200605140438.k4E4c6Mu002995@scanner2.ics.uci.edu>

Dan Nicolaescu wrote:
> This one reappeared after the last xterm.c checkin.
> Is it OK not to check f for NULL here?
>   

No it is not OK.  If someone tries to get the widget tree with editres 
on an Emacs lucid dialog for example, Emacs will crash.  I've checked in 
a fix.

    Jan D.

> CID: 33
> Checker: NULL_RETURNS (help)
> File: base/src/emacs/src/xterm.c
> Function: handle_one_xevent
> Description: Dereferencing NULL value "f"
>
> 5801 	#ifdef HACK_EDITRES
> 5802 	        if (event.xclient.message_type
> 5803 		    == dpyinfo->Xatom_editres)
> 5804 	          {
>
> Event returned_null: Function "x_any_window_to_frame" returned NULL value (checked 8 out of 9 times) [model]
> Event var_assigned: Variable "f" assigned to NULL return value from "x_any_window_to_frame"
> Also see events: [var_assigned][dereference]
>
> 5805 		    f = x_any_window_to_frame (dpyinfo, event.xclient.window);
>
> Event dereference: Dereferencing NULL value "f"
> Also see events: [returned_null][var_assigned]
>
> 5806 	            _XEditResCheckMessages (f->output_data.x->widget, NULL,
> 5807 	                                    &event, NULL);
> 5808 		    goto done;
> 5809 	          }
>
>   

  parent reply	other threads:[~2006-05-14 11:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-14  4:38 Problem report #33 Dan Nicolaescu
2006-05-14 11:03 ` Kim F. Storm
2006-05-14 11:31 ` Jan D. [this message]
2006-05-15 21:46   ` Problem report #33 RESOLVED Kim F. Storm
2006-05-16  6:16     ` Jan Djärv
2006-05-16 11:08       ` Kim F. Storm

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=44671504.9010808@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --cc=emacs-devel@gnu.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).