10-24-2005
Is this a threaded environment? GDB doesn't do well with threads - the version we have anyway.
10 More Discussions You Might Find Interesting
1. Programming
Can anyone give me the link to a website having gdb tutorials
(for advanaced debugging & shortcuts)
http://www.burneddowndays.com/talk/YaBBImages/rolleyes.gif (1 Reply)
Discussion started by: wojtyla
1 Replies
2. HP-UX
Hi,
I'm trying to debug my gcc compiled code on my HPUX 11.23 (Itanium).
I searched the machine to find something that looks like a compiler, and what I found was :
adb (a bit unfriendly for debugging)
kwdb (I understand this is a kernel debugger)
gdb32
gdb64
gdbpa
When I run either... (0 Replies)
Discussion started by: rimon
0 Replies
3. UNIX for Advanced & Expert Users
Hi,
This is a simple question on GDB. Given a core file, how can you check which process has dumped the core?
Regards
- Krishna (1 Reply)
Discussion started by: krishnamurthig
1 Replies
4. UNIX for Advanced & Expert Users
Hi All,
I wanted to know if there is a core file generated and I am not sure for which Binary it is generated .
Can I use gdb to debug the core file ?
Thanks. (1 Reply)
Discussion started by: shubhranshu
1 Replies
5. UNIX for Advanced & Expert Users
Hi All,
I am trying to execute a binary and it is giving Segmentation Fault.
Can I use gdb to debug this error?
Secondly there is no core file generated , so when I an trying to run gdb with the binary only I am not able to set any breakpoints.
When I am running the gdb and the I am... (1 Reply)
Discussion started by: shubhranshu
1 Replies
6. UNIX for Advanced & Expert Users
Hi all
What 's the relationship between gdb and ptrace, if the kernel does
not support ptrace, can gdb work ?
Is there some one can explain this for me (3 Replies)
Discussion started by: yanglei_fage
3 Replies
7. Programming
Hello,
I am having problem with debugging my code. I am writing a C code and then I compile it with the Makefile. I make a target file and then copy it in my Robot(Khepera III) and then run the program over there.
I compile it ofcorse on my machine and then copy the compiled file in the... (10 Replies)
Discussion started by: mind@work
10 Replies
8. Programming
i have created some break points in gdb.
let's say....
b sqlcxt
how can i know the breakpoint name of sqlcxt ??? (1 Reply)
Discussion started by: lipun4u
1 Replies
9. Programming
Hi all,
I was wondering how to find interesting information inside the assembly code. As example, I've been trying something at smashthestack wargame. After viewing the assembly code via disassemble main command, I'm not sure what else to do. Hopefully someone can guide me here.
This is... (2 Replies)
Discussion started by: type8code0
2 Replies
10. Programming
Hi, I got:
host machine: RedHat (RHEL6)
virtual machine: RedHat (RHEL6)
I run (on host machine):
qemu-system-x86_64 ...... -S -s
after that i run (on host machine):
gdb
target remote localhost:1234
set architecture i386:x86-64
and then i can use (on host machine) 'ctrl + c' to... (2 Replies)
Discussion started by: Chrisdot
2 Replies
LEARN ABOUT X11R4
xlockdisplay
XInitThreads(3) XLIB FUNCTIONS XInitThreads(3)
NAME
XInitThreads, XLockDisplay, XUnlockDisplay - multi-threading support
SYNTAX
Status XInitThreads(void);
void XLockDisplay(Display *display);
void XUnlockDisplay(Display *display);
ARGUMENTS
display Specifies the connection to the X server.
DESCRIPTION
The XInitThreads function initializes Xlib support for concurrent threads. This function must be the first Xlib function a multi-threaded
program calls, and it must complete before any other Xlib call is made. This function returns a nonzero status if initialization was suc-
cessful; otherwise, it returns zero. On systems that do not support threads, this function always returns zero.
It is only necessary to call this function if multiple threads might use Xlib concurrently. If all calls to Xlib functions are protected
by some other access mechanism (for example, a mutual exclusion lock in a toolkit or through explicit client programming), Xlib thread ini-
tialization is not required. It is recommended that single-threaded programs not call this function.
The XLockDisplay function locks out all other threads from using the specified display. Other threads attempting to use the display will
block until the display is unlocked by this thread. Nested calls to XLockDisplay work correctly; the display will not actually be unlocked
until XUnlockDisplay has been called the same number of times as XLockDisplay. This function has no effect unless Xlib was successfully
initialized for threads using XInitThreads.
The XUnlockDisplay function allows other threads to use the specified display again. Any threads that have blocked on the display are
allowed to continue. Nested locking works correctly; if XLockDisplay has been called multiple times by a thread, then XUnlockDisplay must
be called an equal number of times before the display is actually unlocked. This function has no effect unless Xlib was successfully ini-
tialized for threads using XInitThreads.
SEE ALSO
Xlib - C Language X Interface
X Version 11 libX11 1.2.1 XInitThreads(3)