Okay, I was being stupid...
I'm off for vacation for a week, so I'll get back to everyone on the 3rd.
Don --------
Here it is:
server2 # ./gdb64 /archive1/rsync 11938 Detected 32-bit executable. Invoking /archive1/gdb32. HP gdb 2.1 Copyright 1986 - 1999 Free Software Foundation, Inc. Hewlett-Packard Wildebeest 2.1 (based on GDB 5.0-hpwdb-20000630) Wildebeest is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for Wildebeest. Type "show warranty" for details. Wildebeest was built for PA-RISC 1.1 or 2.0 (narrow), HP-UX 11.00. .. /archive1/11938: No such file or directory. Attaching to program: /archive1/rsync, process 11938 Reading symbols from /archive1/./rsync...done. Reading symbols from /usr/lib/libc.2...done. Reading symbols from /usr/lib/libdld.2...done.
warning: reading `r3' register: No data 0xc020ccd0 in _select_sys () from /usr/lib/libc.2 (gdb) b _exit_cleanup Breakpoint 1 at 0xb02c: file cleanup.c, line 89. (gdb) c Continuing.
Breakpoint 1, _exit_cleanup (code=11, file=0x555d0 "receiver.c", line=237) at cleanup.c:89 89 cleanup.c: No such file or directory. (gdb) bt #0 _exit_cleanup (code=11, file=0x555d0 "receiver.c", line=237) at cleanup.c:89 #1 0x9b20 in receive_data (f_in=0, mapbuf=0x0, fd=1, fname=0x7f7f18e0 "file1.db", total_size=4304863232) at receiver.c:237 #2 0xa8c4 in recv_files (f_in=0, flist=0x4000bf08, local_name=0x0) at receiver.c:513 #3 0x122f4 in do_recv (f_in=0, f_out=1, flist=0x4000bf08, local_name=0x0) at main.c:477 #4 0x12738 in do_server_recv (f_in=0, f_out=1, argc=1, argv=0x7f7f06d4) at main.c:578 #5 0x12898 in start_server (f_in=0, f_out=1, argc=2, argv=0x7f7f06d0) at main.c:609 #6 0x12790 in child_main (argc=2, argv=0x7f7f06d0) at main.c:585 #7 0x2e0c8 in local_child (argc=2, argv=0x7f7f06d0, f_in=0x7f7f0668, f_out=0x7f7f066c, child_main=0x40004df2 <child_main>) at pipe.c:153 #8 0x11b7c in do_cmd (cmd=0x0, machine=0x0, user=0x0, path=0x4000aee8 "/var/opt/ignite", f_in=0x7f7f0668, f_out=0x7f7f066c) at main.c:319 #9 0x13664 in start_client (argc=1, argv=0x4000aa00) at main.c:911 #10 0x13c74 in main (argc=2, argv=0x4000aa00) at main.c:1110 (gdb)
--------------------------
From: "Don Malloy" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] CC: [EMAIL PROTECTED] Subject: Re: HP-UX 11i and largefiles on rsync 2.6.2 Date: Fri, 23 Jul 2004 12:16:02 -0400
It still shows as bad breakpoint..
server2 # ./gdb /archive1/rsync 6835 HP gdb 2.1 Copyright 1986 - 1999 Free Software Foundation, Inc. Hewlett-Packard Wildebeest 2.1 (based on GDB 5.0-hpwdb-20000630) Wildebeest is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for Wildebeest. Type "show warranty" for details. Wildebeest was built for PA-RISC 1.1 or 2.0 (narrow), HP-UX 11.00. .. /archive1/6835: No such file or directory. Attaching to program: /archive1/rsync, process 6835 Reading symbols from /archive1/./rsync...done. Reading symbols from /usr/lib/libc.2...done. Reading symbols from /usr/lib/libdld.2...done.
warning: reading `r3' register: No data 0xc020ccd0 in _select_sys () from /usr/lib/libc.2 (gdb) enable _exit_cleanup warning: bad breakpoint number at or near '_exit_cleanup' (gdb) enable exit_cleanup warning: bad breakpoint number at or near 'exit_cleanup' (gdb)
Do you have any other ideas for the naming of the breakpoint?
Don
From: Wayne Davison <[EMAIL PROTECTED]> To: Don Malloy <[EMAIL PROTECTED]> CC: [EMAIL PROTECTED] Subject: Re: HP-UX 11i and largefiles on rsync 2.6.2 Date: Thu, 22 Jul 2004 16:29:23 -0700
On Thu, Jul 22, 2004 at 04:27:57PM -0400, Don Malloy wrote: > server2 # ./rsync -a --progress --stats file1.db /var/opt/ignite
What I want is the backtrace when the rsync that is failing dies so we can (hopefully) figure out why it is dying. In the above command the client should be the sender, so it appears to be receiving side that is dying. Unfortunately that means that there are two processes to choose from (the two higher-numbered ones). The best thing to do would be to attach a debugger to both of them (each in a separate window). Set a break-point at _exit_cleanup (I forgot that the function is really named with a leading underscore because of some macro shenanigans), and then tell it to "c"ontinue. You'll be able to get a backtrace of what each program was doing when it either died from a signal or chose to exit. You can look around a bit too (e.g. move "up", "l"ook around, and "p"rint some variables).
..wayne..
_________________________________________________________________
Powerful Parental Controls Let your child discover the best the Internet has to offer. http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=http://hotmail.com/enca&HL=Market_MSNIS_Taglines Start enjoying all the benefits of MSNŽ Premium right now and get the first two months FREE*.
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
_________________________________________________________________
Scan and help eliminate destructive viruses from your inbound and outbound e-mail and attachments. http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=http://hotmail.com/enca&HL=Market_MSNIS_Taglines Start enjoying all the benefits of MSNŽ Premium right now and get the first two months FREE*.
-- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
