Sponsored Content
Full Discussion: When to use Malloc?
Top Forums Programming When to use Malloc? Post 86643 by Tonje on Monday 17th of October 2005 04:40:50 AM
Old 10-17-2005
Thank you very much for your reply. It is "clearer" for me now. Smilie)
 

10 More Discussions You Might Find Interesting

1. Programming

a problem about malloc()

1 . Thanks everyone who read the post. 2 . the programe is that : #include <stdio.h> #include <string.h> void do_it(char *p) { p = (char *) malloc(100); (void )strcpy(p,"1234"); } int main(void) { char *p; do_it(p); (void )printf("p = %s \n",p); (1 Reply)
Discussion started by: chenhao_no1
1 Replies

2. Programming

malloc

hello sir since by mentioning a integer pointer and storing the integers by incrementing the pointer value then what is the purpose of malloc? u can decalre it as in t *p; several integers can be stored by incrementing the value of p, hence what is the diffrence between this... (2 Replies)
Discussion started by: rajashekaran
2 Replies

3. Programming

malloc()

Some one please explain me what is Dynamic memory allocation and the use of malloc() function.How do we allocate memory dynamically and also the other way? (3 Replies)
Discussion started by: rash123
3 Replies

4. Programming

Malloc implementation in C

Hey Guys I am trying to implement the malloc function for my OS class and I am having a little trouble with it. I would be really grateful if I could get some hints on this problem. So I am using a doubly-linked list as my data structure and I have to allocate memory for it (duh...). The... (1 Reply)
Discussion started by: Gambit_b
1 Replies

5. UNIX for Advanced & Expert Users

Malloc Implementation in C

Hey Guys Some of my friends have got together and we are trying to write a basic kernel similar to Linux. I am trying to implement the malloc function in C and I am using a doubly linked list as the primary data structure. I need to allocate memory for this link list (duh...) and I don't feel... (2 Replies)
Discussion started by: rbansal2
2 Replies

6. Programming

malloc vs realloc

Why when using realloc, john is reversed 3 times but not the other 2 names ? But if I use malloc, then the 3 names are reversed correctly ? (but then there is a memory leak) How can I reverse all 3 names without a memory leak ? char *BUFFER = NULL; char *STRREVERSE(const char *STRING) {... (5 Replies)
Discussion started by: cyler
5 Replies

7. UNIX for Dummies Questions & Answers

Kmalloc and malloc

Do kmalloc and malloc allocate from same heap ? (3 Replies)
Discussion started by: dragonpoint
3 Replies

8. Programming

help with malloc [solved]

Hi i found code in google how to malloc an 2D array and i tried that : #include<stdio.h> #include<stdlib.h> int **A; int **B; int main(int argc,char *argv) { printf("name of text : %s\n",argv); //read arrays int i,j; int l,m; int M,n; FILE *fp; fp=fopen(argv,"r"); ... (0 Replies)
Discussion started by: giampoul
0 Replies

9. Programming

malloc vs new speed

Which one is faster among malloc and new? My understanding is that since new also has to call constructors after allocating memory it must be slower than malloc. Am I correct? (1 Reply)
Discussion started by: rupeshkp728
1 Replies

10. UNIX for Dummies Questions & Answers

Help with malloc()

Good day! I'm a newbie in C. I'm trying to get an unlimited input from the user using malloc then printing the inputs after the user presses enter. My code works, but there's a warning that I don't know how to fix. Please help me. Thank you. Here's my code: #include <stdio.h> #include... (6 Replies)
Discussion started by: eracav
6 Replies
xcb_randr_get_screen_resources(3)				   XCB Requests 				 xcb_randr_get_screen_resources(3)

NAME
xcb_randr_get_screen_resources - SYNOPSIS
#include <xcb/randr.h> Request function xcb_randr_get_screen_resources_cookie_t xcb_randr_get_screen_resources(xcb_connection_t *conn, xcb_window_t window); Reply datastructure typedef struct xcb_randr_get_screen_resources_reply_t { uint8_t response_type; uint8_t pad0; uint16_t sequence; uint32_t length; xcb_timestamp_t timestamp; xcb_timestamp_t config_timestamp; uint16_t num_crtcs; uint16_t num_outputs; uint16_t num_modes; uint16_t names_len; uint8_t pad1[8]; } xcb_randr_get_screen_resources_reply_t; Reply function xcb_randr_get_screen_resources_reply_t *xcb_randr_get_screen_resources_reply(xcb_connection_t *conn, xcb_randr_get_screen_resources_cookie_t cookie, xcb_generic_error_t **e); Reply accessors xcb_randr_crtc_t *xcb_randr_get_screen_resources_crtcs(const xcb_randr_get_screen_resources_request_t *reply); int xcb_randr_get_screen_resources_crtcs_length(const xcb_randr_get_screen_resources_reply_t *reply); xcb_generic_iterator_t xcb_randr_get_screen_resources_crtcs_end(const xcb_randr_get_screen_resources_reply_t *reply); xcb_randr_output_t *xcb_randr_get_screen_resources_outputs(const xcb_randr_get_screen_resources_request_t *reply); int xcb_randr_get_screen_resources_outputs_length(const xcb_randr_get_screen_resources_reply_t *reply); xcb_generic_iterator_t xcb_randr_get_screen_resources_outputs_end(const xcb_randr_get_screen_resources_reply_t *reply); xcb_randr_mode_info_t *xcb_randr_get_screen_resources_modes(const xcb_randr_get_screen_resources_request_t *reply); int xcb_randr_get_screen_resources_modes_length(const xcb_randr_get_screen_resources_reply_t *reply); xcb_randr_mode_info_iterator_t xcb_randr_get_screen_resources_modes_iterator(const xcb_randr_get_screen_resources_reply_t *reply); uint8_t *xcb_randr_get_screen_resources_names(const xcb_randr_get_screen_resources_request_t *reply); int xcb_randr_get_screen_resources_names_length(const xcb_randr_get_screen_resources_reply_t *reply); xcb_generic_iterator_t xcb_randr_get_screen_resources_names_end(const xcb_randr_get_screen_resources_reply_t *reply); REQUEST ARGUMENTS
conn The XCB connection to X11. window TODO: NOT YET DOCUMENTED. REPLY FIELDS
response_type The type of this reply, in this case XCB_RANDR_GET_SCREEN_RESOURCES. This field is also present in the xcb_generic_reply_t and can be used to tell replies apart from each other. sequence The sequence number of the last request processed by the X11 server. length The length of the reply, in words (a word is 4 bytes). timestamp TODO: NOT YET DOCUMENTED. config_timestamp TODO: NOT YET DOCUMENTED. num_crtcs TODO: NOT YET DOCUMENTED. num_outputs TODO: NOT YET DOCUMENTED. num_modes TODO: NOT YET DOCUMENTED. names_len TODO: NOT YET DOCUMENTED. DESCRIPTION
RETURN VALUE
Returns an xcb_randr_get_screen_resources_cookie_t. Errors have to be handled when calling the reply function xcb_randr_get_screen_re- sources_reply. If you want to handle errors in the event loop instead, use xcb_randr_get_screen_resources_unchecked. See xcb-requests(3) for details. ERRORS
This request does never generate any errors. SEE ALSO
AUTHOR
Generated from randr.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. XCB
2014-06-10 xcb_randr_get_screen_resources(3)
All times are GMT -4. The time now is 02:29 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy