Sponsored Content
Full Discussion: Debug two process Using GDB
Top Forums Programming Debug two process Using GDB Post 302299100 by mr_deb on Thursday 19th of March 2009 08:00:02 AM
Old 03-19-2009
Debug two process Using GDB

Hi All
I know How to attach a process to beubg it .But for my application I am using client as well server.Both are two separate process .Suppose I need to debug both .How to attach both of them together .Or I have to attach them separetly .

Suppose client process id is 1325 and server is 1355.
Can use
gdb attach 1325 1355.

Please suggest me
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

gdb to child process

Hi, I want to debug a child process which is forked from other process. Whenever I try to attach the pid of child process to gbd, the process gets killed and the parent process starts a new child process. any idea what could be the reason. In general how can i debug a child process... (4 Replies)
Discussion started by: shriashishpatil
4 Replies

2. Programming

gdb: how to debug an executable file with a few command line papameters

If an executalbe file has several parameters, gdb can not pass parameters correctly. Let us see: run: ./executablefile1 agr1 arg2 arg3 debug: gdb executablefile1 run executalbefile1 arg1 arg2 arg3 then argv : executablefile1 argv : executablefile argv : arg1 ... (3 Replies)
Discussion started by: cdbug
3 Replies

3. Programming

gdb: problem while debug an executable file

I created one file (test.cpp)and complied it and get the executable file(test) and run it.It is giving the out put but when I am trying to debug that executable.I am getting the error -- please tell me the solutions?? Thanks in advance ..... (2 Replies)
Discussion started by: smartgupta
2 Replies

4. UNIX for Advanced & Expert Users

Gdb:

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

5. UNIX for Advanced & Expert Users

a question about debug using gdb(/lib32/libc.so.6: No such file or directory)

Hi all, (gdb) target remote 192.168.185.196:1389 Remote debugging using 192.168.185.196:1389 warning: Unable to find dynamic linker breakpoint function. GDB will be unable to debug shared library initializers and track explicitly loaded dynamic code. 0x2fbd0800 in ?? () (gdb) l 1 ... (0 Replies)
Discussion started by: yanglei_fage
0 Replies

6. 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

7. Programming

gdb help

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

8. Programming

Can't debug: assert error with gdb (no problem without)

I'm sorry if the title is really criptic, but I don't know how to phrase my problem. I know I can't really ask for a solution, and I normally wouldn't but this is really escaping my abilities. Antefacts. I developed a program using the zeromq messaging library. I got to a point where the... (11 Replies)
Discussion started by: erupter
11 Replies

9. UNIX for Dummies Questions & Answers

How to stop debug in the mid of process?

Hi Gurus, I am debugging a script. it loops filelist. since the list a very long. when debugging, I only can see the last a few lines. is there any way to stop debuger in the mid of process. the command I used for debugging is: ksh -x scriptName Thanks in advance (7 Replies)
Discussion started by: ken6503
7 Replies

10. Programming

Odd behavior from GDB while trying to cross-debug an embedded Linux application.

Some background: The application normally runs on an embedded platform. Currently, for development purposes, I have the rootfs located @ /exports and the target is communicating over NFS. That way I can make a change on my local system, save the application @ /exports, and run the altered... (4 Replies)
Discussion started by: Circuits
4 Replies
socal(7D)							      Devices								 socal(7D)

NAME
socal - Serial Optical Controller for Fibre Channel Arbitrated Loop (SOC+) device driver SYNOPSIS
socal@sbus-slot,0 DESCRIPTION
The Fibre Channel Host Bus Adapter is an SBus card which implements two full duplex Fibre Channel interfaces. Each Fibre Channel interface can connect to a Fibre Channel Arbitrated Loop (FC-AL). The socal device driver is a nexus driver and implements portions of the FC-2 and FC-4 layers of FC-AL. FILES
/kernel/drv/socal ELF Kernel Module ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Architecture |SPARC | +-----------------------------+-----------------------------+ SEE ALSO
sbus(4), sf(7D), ssd(7D) Writing Device Drivers ANSI X3.230-1994, Fibre Channel Physical and Signalling Interface (FC-PH) ANSI X3.272-1996, Fibre Channel Arbitrated Loop (FC-AL) Fibre Channel Private Loop SCSI Direct Attach (FC-PLDA) DIAGNOSTICS
The messages described below may appear on system console in addition to being logged. On the console, these messages are preceded by: socal%d: port %a where %d is the instance number of the socal controller and %a is the port on the host adapter. Fibre Channel Loop is ONLINE The Fibre Channel loop is now online. Fibre Channel Loop is OFFLINE The Fibre Channel loop is now offline. attach failed: device in slave-only slot. Move soc+ card to another slot. attach failed: bad soft state. Driver did not attach, devices will be inaccessible. attach failed: unable to alloc xport struct. Driver did not attach, devices will be inaccessible. attach failed: unable to map eeprom Driver was unable to map device memory; check for bad hardware. Driver did not attach to device, devices will be inaccessible. attach failed: unable to map XRAM Driver was unable to map device memory; check for bad hardware. Driver did not attach to device, devices will be inaccessible. attach failed: unable to map registers Driver was unable to map device registers; check for bad hardware. Driver did not attach to device, devices will be inaccessible. attach failed: unable to access status register Driver was unable to map device registers; check for bad hardware. Driver did not attach to device, devices will be inaccessible. attach failed: unable to install interrupt handler Driver was not able to add the interrupt routine to the kernel. Driver did not attach to device, devices will be inaccessible. attach failed: unable to access host adapter XRAM Driver was unable to access device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible. attach failed: unable to write host adapter XRAM Driver was unable to write device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible. attach failed: read/write mismatch in XRAM Driver was unable to verify device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible. SunOS 5.11 9 May 1997 socal(7D)
All times are GMT -4. The time now is 02:35 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy