Sponsored Content
Top Forums Programming AIX 5.3 64-bit program crashes with AIX 5.1 Post 302133539 by jeet_xp on Friday 24th of August 2007 12:52:08 AM
Old 08-24-2007
Thanks porter for your reply, I understood what you wanted to say. Can you please tell me where can I find what all got changed from one release to other?
 

10 More Discussions You Might Find Interesting

1. AIX

AIX 5.3 , gensyms command, translate 32 bit addr to 64 bit addr

I am trying to map the information from the gensyms command, Its gives information about the various symbols info like symbol type, addr offset, and the main libraries addr starting point. My problem is , how do I map this 32 bit addr to a 64 bit addr, I am trying to extract Segment # information... (0 Replies)
Discussion started by: mrmeswani
0 Replies

2. AIX

pthread library on AIX 5.3 64 bit

Hi, I am running my application on two AIX 5.3 64 bit boxes. In one of the boxes it is running fine without any problems. But on the other box it fails as soon as it is started and it core dumps. When I was analysing the core I was able to find the below two lines in addition to other... (4 Replies)
Discussion started by: allthanksquery
4 Replies

3. AIX

porting an application on 64-bit AIX version 5

Hi all, I am facing problem in porting to 64 bit AIX especially with compiling options to compile and run under 64 bit kernel.Can any one put some light on the issue thanks in advance vishal (14 Replies)
Discussion started by: vishalzone2002
14 Replies

4. AIX

Segmentation fault in nsgetcinfo in aix 64-bit c code

Hello, I am running on a AIX5.2 server with Oracle 10g and 9i. My code compiles and works fine in 32-bit mode. The same code compiles in 64-bit and runs good. The program catches CNTRL-C signal to terminate. Only on 64-bit code when i hit CNTRL-C, the program exits with segmentation... (0 Replies)
Discussion started by: sumesh0710
0 Replies

5. AIX

AIX OS bit info

Hi All, How do i find a bit info whether 32 bit or 64 bit of AIX operating system? Please help R (6 Replies)
Discussion started by: tenderfoot
6 Replies

6. Programming

C++ program crashes

Hi, Could anyone tell me the reason why the following program crashes? class A { int x; public: A() { cout << "from A()" << endl; } ~A() { cout << "from ~A()" << endl; } }; class B : public A { public: B() { cout << "from B()"... (2 Replies)
Discussion started by: royalibrahim
2 Replies

7. AIX

Unix 64-bit AIX V6.1 Standard Edition

Unix 64bit AIX v6.1 standard edition what do you mean ? function ? pls, help me... (1 Reply)
Discussion started by: khanhphv
1 Replies

8. Programming

C++ program crashes

Hi, Can anyone tell me why the below program is crashing? and where exactly it is crashing. What is the corrective measure to be taken to make it work fine? #include <iostream> #include <cstring> using namespace std; class CString { char* m_data; public: CString() :... (6 Replies)
Discussion started by: royalibrahim
6 Replies

9. AIX

32 bit app on aix 6.1

We have our in house developed software running on AIX 6.1 (6100-06-06-1140). The application is a 32 bit application and the operating system is 64 bit. We are running this application without any issue on AIX 5.3 32-bit on P5. We are facing issue with this application after moving on P7 with aix... (4 Replies)
Discussion started by: vjm
4 Replies

10. UNIX for Beginners Questions & Answers

Java 32 bit installation fails on an AIX platform

Hello. It is my first to deal with Java installation on an AIX platform. I am now trying to install Java 32bit using installp command. However, it throws back the message that the installation media cannot be found. I need to install Java 32bit to proceed with an installation of Oracle JD... (0 Replies)
Discussion started by: EJ2019
0 Replies
xcb_xkb_get_device_info(3)					   XCB Requests 					xcb_xkb_get_device_info(3)

NAME
xcb_xkb_get_device_info - SYNOPSIS
#include <xcb/xkb.h> Request function xcb_xkb_get_device_info_cookie_t xcb_xkb_get_device_info(xcb_connection_t *conn, xcb_xkb_device_spec_t deviceSpec, uint16_t wanted, uint8_t allButtons, uint8_t firstButton, uint8_t nButtons, xcb_xkb_led_class_spec_t ledClass, xcb_xkb_id_spec_t ledID); Reply datastructure typedef struct xcb_xkb_get_device_info_reply_t { uint8_t response_type; uint8_t deviceID; uint16_t sequence; uint32_t length; uint16_t present; uint16_t supported; uint16_t unsupported; uint16_t nDeviceLedFBs; uint8_t firstBtnWanted; uint8_t nBtnsWanted; uint8_t firstBtnRtrn; uint8_t nBtnsRtrn; uint8_t totalBtns; uint8_t hasOwnState; uint16_t dfltKbdFB; uint16_t dfltLedFB; uint8_t pad0[2]; xcb_atom_t devType; uint16_t nameLen; } xcb_xkb_get_device_info_reply_t; Reply function xcb_xkb_get_device_info_reply_t *xcb_xkb_get_device_info_reply(xcb_connection_t *conn, xcb_xkb_get_device_info_cookie_t cookie, xcb_generic_error_t **e); Reply accessors xcb_xkb_string8_t *xcb_xkb_get_device_info_name(const xcb_xkb_get_device_info_request_t *reply); int xcb_xkb_get_device_info_name_length(const xcb_xkb_get_device_info_reply_t *reply); xcb_generic_iterator_t xcb_xkb_get_device_info_name_end(const xcb_xkb_get_device_info_reply_t *reply); xcb_xkb_action_t *xcb_xkb_get_device_info_btn_actions(const xcb_xkb_get_device_info_request_t *reply); int xcb_xkb_get_device_info_btn_actions_length(const xcb_xkb_get_device_info_reply_t *reply); xcb_xkb_action_iterator_t xcb_xkb_get_device_info_btn_actions_iterator(const xcb_xkb_get_device_info_reply_t *reply); int xcb_xkb_get_device_info_leds_length(const xcb_xkb_get_device_info_reply_t *reply); xcb_xkb_device_led_info_iterator_t xcb_xkb_get_device_info_leds_iterator(const xcb_xkb_get_device_info_reply_t *reply); REQUEST ARGUMENTS
conn The XCB connection to X11. deviceSpec TODO: NOT YET DOCUMENTED. wanted TODO: NOT YET DOCUMENTED. allButtons TODO: NOT YET DOCUMENTED. firstButton TODO: NOT YET DOCUMENTED. nButtons TODO: NOT YET DOCUMENTED. ledClass TODO: NOT YET DOCUMENTED. ledID TODO: NOT YET DOCUMENTED. REPLY FIELDS
response_type The type of this reply, in this case XCB_XKB_GET_DEVICE_INFO. 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). deviceID TODO: NOT YET DOCUMENTED. present TODO: NOT YET DOCUMENTED. supported TODO: NOT YET DOCUMENTED. unsupported TODO: NOT YET DOCUMENTED. nDeviceLedFBs TODO: NOT YET DOCUMENTED. firstBtnWanted TODO: NOT YET DOCUMENTED. nBtnsWanted TODO: NOT YET DOCUMENTED. firstBtnRtrn TODO: NOT YET DOCUMENTED. nBtnsRtrn TODO: NOT YET DOCUMENTED. totalBtns TODO: NOT YET DOCUMENTED. hasOwnState TODO: NOT YET DOCUMENTED. dfltKbdFB TODO: NOT YET DOCUMENTED. dfltLedFB TODO: NOT YET DOCUMENTED. devType TODO: NOT YET DOCUMENTED. nameLen TODO: NOT YET DOCUMENTED. DESCRIPTION
RETURN VALUE
Returns an xcb_xkb_get_device_info_cookie_t. Errors have to be handled when calling the reply function xcb_xkb_get_device_info_reply. If you want to handle errors in the event loop instead, use xcb_xkb_get_device_info_unchecked. See xcb-requests(3) for details. ERRORS
This request does never generate any errors. SEE ALSO
AUTHOR
Generated from xkb.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. XCB
2014-06-10 xcb_xkb_get_device_info(3)
All times are GMT -4. The time now is 02:35 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy