Sponsored Content
Operating Systems Linux Red Hat Gdb error while debugging core file Post 302892505 by sanzee007 on Thursday 13th of March 2014 05:59:36 AM
Old 03-13-2014
Hi,
Thanks for the reply, but it did not work me. I think problem is somewhere else.

thanks
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Using GDB to analyse different CORE dumps

Hi, Can we modify the GDB source code so as to analyze core dumps from different targets? From my analysis, I think we need to build our section table statically for each target. i.e., including the various address boundaries in build_section_table() function. If this is the case, then the GDB... (2 Replies)
Discussion started by: nsdeeps
2 Replies

2. Programming

Debugging 64bit code with gdb and ddd in AIX

I'm trying to use the GDB debugger and DDD to debug 64bit code. It seems that the AIX toolkit gdb version 6.0 works with 64bit code. But the ddd tool when running gdb gives the following errors : Starting program: <my binary> <my params> warning: "": not in executable format: There is an input... (2 Replies)
Discussion started by: bean66
2 Replies

3. UNIX for Dummies Questions & Answers

Debugging core file from another server

Hi all, One fine day one of the services in our prod server started core dumping and then the core file was ftp'd to our test server , to debug we used gdb with the executable which we had but we could not get the function names ( maybe due to missing symbols ) How do i solve this ... (1 Reply)
Discussion started by: diasgeorge
1 Replies

4. Programming

Debugging a running process in GDB

Hi , Any gdb user could see my problem. Let me describe what i want to do. i have a test utility to send message to running process. My interest is to go through to functions calls when my test case starts. In a simple way i want have a code walk for a particular scenario of a test... (1 Reply)
Discussion started by: meet123321
1 Replies

5. Linux

unable to read core dumps on unix. Is there another way than using GDB?

hi all, I am having set of core dumps obtained from client server. Now i am trying to read them but unable to do so. I have few queries: 1. Core dumps were generated on some xyz server and copied to my unix virtual. Can I read them as text here? 2. I tried installing gdb-7.3 but when i fire... (0 Replies)
Discussion started by: suyogs
0 Replies

6. UNIX for Dummies Questions & Answers

GDB Debugging Problem

I have added some code in my file. I have created executable rpm file of our code and also I have created debuginfo and debugsource files and installed all three. But when I debug in gdb I see the the code changes in soucre file. But the break point does not hit at that place as if it did not... (1 Reply)
Discussion started by: rupeshkp728
1 Replies

7. Programming

64 bit code debugging using gdb and ddd

Hello I have built our application on AIX 7.1 as a 64 bit application. My queries are as follows: Can a 32bit gdb (v7.6) and ddd (data display debugger - v3.3.12), debug a 64bit executable ? If I have a small 64bit a.exe executable that seems to work. If I have a more complicated executable... (4 Replies)
Discussion started by: biju64
4 Replies

8. Programming

Best guide or video for gdb <register level debugging>

would like to know best guide or document for gdb for different architectures x86 , power pc etc.. would like to understand how to debug segmentation faults because of stack corruption .. understand utilities ELF , objdump etc.. please guide me (1 Reply)
Discussion started by: Gopi Krishna P
1 Replies

9. Programming

Best reference for understanding core file and debugging for different architectures

Hi , could someone suggest best reference for core file understanding , analysis , debugging for different architectures like what registers represent what in a architecture specific core .. how to get maximum information out of corrupted core different tools and how they work and how to... (1 Reply)
Discussion started by: Gopi Krishna P
1 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 09:38 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy