Cannot get dbx to work correctly with a running process


 
Thread Tools Search this Thread
Top Forums Programming Cannot get dbx to work correctly with a running process
# 1  
Old 02-25-2011
Cannot get dbx to work correctly with a running process

Hi everyone,

I've been struggling with this for a few weeks now. I'm trying to debug a running process with dbx on an AIX box.

The command I'm using is 'dbx -a <pid> core'
There is a function I can perform in my application that crashes this process, but it does not show up as crashed in dbx. However, if I do 'ps -ef | grep <process>' it shows a new PID, so I know something is happening. The output I get when I first start dbx is,

Quote:
Waiting to attach to process 573546 ...
Successfully attached to dps643.
Type 'help' for help.
reading symbolic information ...
stopped in msgrcv at 0x900000000247918 ($t1)
0x900000000247918 (msgrcv+0xd8) e8410028 ld r2,0x28(r1)
(dbx)
If anyone can give me a hand, I'd appreciate it.

---------- Post updated at 12:29 PM ---------- Previous update was at 12:09 PM ----------

Another thing I just noticed is, the PID doesn't change until I actually type 'quit' in dbx. The service appears to crash (application locks up - then displays connection lost message), but the PID doesn't change until I exit my dbx session. Don't know if that matters.
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Why does this awk script not work correctly?

I have a large database with English on the left hand side and Indic words on the left hand. It so happens that since the Indic words have been entered by hand, there are duplicates in the entries. The structure is as under: English headword=Indic gloss,Indic gloss A small sample will... (6 Replies)
Discussion started by: gimley
6 Replies

2. Shell Programming and Scripting

Work with setsid to open a session and close it correctly

I would like to create the following script: run a python script with setsid python may or may not fail with exception check if all of the group processes were terminated correctly if not, kill the remaining processes How can I do that? Thanks a lot (3 Replies)
Discussion started by: ASF Studio
3 Replies

3. Gentoo

LDAP-Auth does not work correctly with systemd

Hi, since the upgrade to Gnome 3.6 (now i have 3.8) the authentication over LDAP stops working. The whole machine does not start anymore. The machine boot, but no gdm and no X. I can login, with root, but then the tty hangs. When i look at ttyF12 i see a lot of systemd service the runs random,... (1 Reply)
Discussion started by: darktux
1 Replies

4. SCO

Set NIC correctly , but the network does not work

I'm trying to virtualize an instance of SCO Open Server 5.0.2c in VirtualBox (called VM- A) , I can not configure the network (NIC). The NIC I'm using is PCnet -FAST III (Am79C973 ) (this NIC works with VirtualBox + SCO 5.0.5M) When I add from ' Add new LAN adapter' I detects the NIC... (2 Replies)
Discussion started by: flako
2 Replies

5. UNIX for Advanced & Expert Users

Libvirt does not work correctly anymore on my gentoo

Hi, Since a year my libvirtd does not work anymore on my Gentoodesktop. In the meantime a used virtualbox. But I would like to have back libvirt. The problem was after libvirt should not only work with root privileges. I deinstalled all things with libvirt an kvm. I removed all things from /var... (4 Replies)
Discussion started by: darktux
4 Replies

6. Programming

AIX dbx - attaching to a process that is crashing

Hey everyone, I'm trying to attach to a process that is crashing so I can debug the source code. I've tried this: dbx -a PID stop at "file.cpp":line# However, nothing ever breaks. The service crashes and restarts, but I never see it hitting the code. I've tried to use a core file, but... (2 Replies)
Discussion started by: ctote
2 Replies

7. Programming

dbx - attach to process, break when crash

Hey everyone, I have a process that is crashing, and I'd like to have some way to see where it crashes. Is this possible? (2 Replies)
Discussion started by: ctote
2 Replies

8. Shell Programming and Scripting

Script not running correctly

Hi all, My script below was working fine till I changed the LOGFILE path (which originally points to a file within the same folder of the script for testing) Only the event.log file path is changed, the rest are still within the current folder. Before the change, running the script works.... (1 Reply)
Discussion started by: phixsius
1 Replies

9. Programming

question with running dbx

If your program unfortunately takes a LONG time to finish running in dbx and you find yourself hitting Ctrl+C or Ctrl+Z to stop the running, does it produce any adverse effects at all ? The reason I am asking is because my program is in an infinite loop state (which leads to the huge delay in... (1 Reply)
Discussion started by: JamesGoh
1 Replies

10. SuSE

vsft doesn't work correctly

I install vsftpd server on 2 SUSE 10.2 servers. The first works perfectly, but the second doesn't work how I expect. The second works only over local network and doesn't over internet. The vsftpd.conf and ../xinetd.d/vsftpd are the same in 2 servers. The only different was when I threw to log in... (1 Reply)
Discussion started by: zhivko.neychev
1 Replies
Login or Register to Ask a Question
BTRACEBACK(1)					     Network backup, recovery and verification					     BTRACEBACK(1)

NAME
btraceback - wrapper script around gdb and bsmtp SYNOPSIS
btraceback /path/to/binary pid DESCRIPTION
btraceback is a wrapper shell script around the gdb debugger (or dbx on Solaris systems) and bsmtp, provided for debugging purposes. USAGE
btraceback is called by the exception handlers of the Bacula daemons during a crash. It can also be called interactively to view the cur- rent state of the threads belonging to a process, but this is not recommended unless you are trying to debug a problem (see below). NOTES
In order to work properly, debugging symbols must be available to the debugger on the system, and gdb, or dbx (on Solaris systems) must be available in the $PATH. If the Director or Storage daemon runs under a non-root uid, you will probably need to be modify the btraceback script to elevate privi- leges for the call to gdb/dbx, to ensure it has the proper permissions to debug when called by the daemon. Although Bacula's use of btraceback within its exception handlers is always safe, manual or interactive use of btraceback is subject to the same risks than live debugging of any program, which means it could cause Bacula to crash under rare and abnormal circumstances. Conse- quently we do not recommend manual use of btraceback in production environments unless it is required for debugging a problem. ENVIRONMENT
btracback relies on $PATH to find the debugger. FILES
/usr/lib/bacula/btraceback The script itself. /usr/sbin/btraceback symbolic link to /usr/lib/bacula/btraceback /etc/bacula/scripts/btraceback.gdb the GDB command batch used to output a stack trace AUTHOR
This manual page was written by Lucas B. Cohen <lbc@members.fsf.org> SEE ALSO
bsmtp(1) Kern Sibbald 6 December 2009 BTRACEBACK(1)