Groups | Search | Server Info | Login | Register
Groups > comp.windows.x > #451
| From | scott@slp53.sl.home (Scott Lurndal) |
|---|---|
| Subject | Re: XDestroyImage() |
| Newsgroups | comp.unix.programmer, comp.windows.x |
| References | <uiqsp7$54ll$1@dont-email.me> |
| Message-ID | <K084N.102$ayBd.16@fx07.iad> (permalink) |
| Organization | UsenetServer - www.usenetserver.com |
| Date | 2023-11-12 17:34 +0000 |
Cross-posted to 2 groups.
Muttley@dastardlyhq.com writes: >Hello > >I'm a bit uncertain from the man page and from googling around whether >XDestroyImage() only frees the XImage structure created by XCreateImage() >or whether it also frees the user allocated memory that gets passed into >XCreateImage(). > >Anyone know? Kalevi answered. To obtain an answer this question you could have run the application under valgrind - it would tell you about any memory that hadn't been deallocated at exit (using the leak check option).
Back to comp.windows.x | Previous | Next — Previous in thread | Next in thread | Find similar
XDestroyImage() Muttley@dastardlyhq.com - 2023-11-12 15:59 +0000
Re: XDestroyImage() kalevi@kolttonen.fi (Kalevi Kolttonen) - 2023-11-12 16:20 +0000
Re: XDestroyImage() Muttley@dastardlyhq.com - 2023-11-12 16:30 +0000
Re: XDestroyImage() James Kuyper <jameskuyper@alumni.caltech.edu> - 2023-11-12 12:24 -0500
Re: XDestroyImage() Muttley@dastardlyhq.com - 2023-11-13 11:05 +0000
Re: XDestroyImage() Winston <wbe@UBEBLOCK.psr.com.invalid> - 2023-11-13 11:53 -0500
Re: XDestroyImage() Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2023-11-13 11:35 -0800
Re: XDestroyImage() Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-11-15 12:32 +0000
Re: XDestroyImage() scott@slp53.sl.home (Scott Lurndal) - 2023-11-12 17:34 +0000
Re: XDestroyImage() candycanearter07 <no@thanks.net> - 2023-11-12 19:11 -0600
Re: XDestroyImage() Muttley@dastardlyhq.com - 2023-11-13 11:06 +0000
Re: XDestroyImage() scott@slp53.sl.home (Scott Lurndal) - 2023-11-13 14:59 +0000
Re: XDestroyImage() Muttley@dastardlyhq.com - 2023-11-13 15:57 +0000
csiph-web