Date: Sun, 28 Oct 2001 18:37:46 -0800 (PST) From: k Macy <kip_macy@yahoo.com> To: freebsd-hackers@freebsd.org Subject: problems with recurring SIGTRAP under gdb Message-ID: <20011029023746.94559.qmail@web14001.mail.yahoo.com>
index | next in thread | raw e-mail
Any idea why when I insert a breakpoint I get a
SIGTRAP
and can't continue any further? Is this a bug in the
FreeBSD distribution's gdb? I don't see this behavior
on any other platform that I am using. (Linux/
Solaris/
OSF1)
I am only seeing on this particular application. The
binary is 60MB dynamically linked (its 200MB on
Solaris) it is linked against libc_r but I am
currently
running it single threaded.
Any thoughts on correcting this would be much
appreciated.
This is 4.4-STABLE Cvsupped 2 weeks ago.
%r gdb maytag.Rd
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB 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 GDB. Type "show
warranty" for details.
This GDB was configured as "i386-unknown-freebsd"...
(gdb) b pf_open
Breakpoint 1 at 0x804c6ae: file
../sim/freebsd/pf/pf.c, line 204.
(gdb) r -zqp1
Starting program:
/amd/ayr/vol/users2/home/kmacy/kmacy8/maytag.Rd -zqp1
No boot-time filesystem
(/u/kmacy/p4/ontap/control4/prod/build/bfs.Rd) found.
Using ethaddr 00:01:00:00:05:e3
Mon Oct 29 02:16:34 GMT [main_proc:info]: EMS engine
initialized
My sysid = 0x1
Partner sysid = 0x0
Mon Oct 29 02:16:34 GMT [main_proc:notice]: ,tapes not
found: skipping tape simulator initialization.
floppy boot? y
/etc/modules/sample.mod : can't open : Device not
configured
NetApp Release
/amd/raiders/vol/data2/build/scratch/kmacy/control4.561.295_22_34_40:
Sun Oct 28 17:56:19 PST 2001
Copyright (c) 1992-2001 Network Appliance, Inc.
Starting boot on Mon Oct 29 02:16:34 GMT 2001
DBG:disk_mode_sense_fc_page: v0.0 setting FC mode to
40
DBG:disk_mode_sense_fc_page: v0.1 setting FC mode to
40
DBG:disk_mode_sense_fc_page: v0.4 setting FC mode to
40
DBG:disk_mode_sense_fc_page: v0.5 setting FC mode to
40
DBG:disk_mode_sense_fc_page: v0.8 setting FC mode to
40
DBG:disk_mode_sense_fc_page: v0.9 setting FC mode to
40
DBG:disk_mode_sense_fc_page: v0.10 setting FC mode to
40
DBG:disk_mode_sense_fc_page: v0.11 setting FC mode to
40
DBG:disk_mode_sense_fc_page: v0.12 setting FC mode to
40
DBG:disk_mode_sense_fc_page: v0.13 setting FC mode to
40
DBG:disk_mode_sense_fc_page: v0.14 setting FC mode to
40
DBG:disk_mode_sense_fc_page: v0.16 setting FC mode to
40
DBG:disk_mode_sense_fc_page: v0.17 setting FC mode to
40
DBG:disk_mode_sense_fc_page: v0.18 setting FC mode to
40
DBG:disk_mode_sense_fc_page: v0.19 setting FC mode to
40
DBG:disk_mode_sense_fc_page: v0.20 setting FC mode to
40
DBG:disk_mode_sense_fc_page: v0.21 setting FC mode to
40
DBG:disk_mode_sense_fc_page: v0.6 setting FC mode to
40
DBG:disk_mode_sense_fc_page: v1.16 setting FC mode to
40
DBG:disk_mode_sense_fc_page: v1.0 setting FC mode to
40
DBG:disk_mode_sense_fc_page: v1.1 setting FC mode to
40
DBG:disk_mode_sense_fc_page: v1.11 setting FC mode to
40
DBG:disk_mode_sense_fc_page: v1.12 setting FC mode to
40
DBG:disk_mode_sense_fc_page: v1.14 setting FC mode to
40
DBG:disk_mode_sense_fc_page: v1.4 setting FC mode to
40
DBG:disk_mode_sense_fc_page: v1.6 setting FC mode to
40
DBG:disk_mode_sense_fc_page: v1.8 setting FC mode to
40
DBG:disk_mode_sense_fc_page: v1.10 setting FC mode to
40
DBG:disk_mode_sense_fc_page: v1.2 setting FC mode to
40
DBG:disk_mode_sense_fc_page: v1.5 setting FC mode to
40
DBG:disk_mode_sense_fc_page: v1.13 setting FC mode to
40
DBG:disk_mode_sense_fc_page: v1.17 setting FC mode to
40
DBG:disk_mode_sense_fc_page: v1.9 setting FC mode to
40
DBG:disk_mode_sense_fc_page: v1.3 setting FC mode to
40
DBG:disk_mode_sense_fc_page: v1.18 setting FC mode to
40
DBG:disk_mode_sense_fc_page: v1.19 setting FC mode to
40
DBG:disk_mode_sense_fc_page: v1.20 setting FC mode to
40
DBG:disk_mode_sense_fc_page: v1.21 setting FC mode to
40
Breakpoint 1, pf_open (unit=0x0, ethaddrs=0x299570b0
"", valid_addrs=0x29957090) at
../sim/freebsd/pf/pf.c:204
204 int n = 0;
(gdb) n
Program received signal SIGTRAP, Trace/breakpoint
trap.
pf_open (unit=0x0, ethaddrs=0x299570b0 "",
valid_addrs=0x29957090) at ../sim/freebsd/pf/pf.c:204
204 int n = 0;
(gdb) n
Program received signal SIGTRAP, Trace/breakpoint
trap.
pf_open (unit=0x0, ethaddrs=0x299570b0 "",
valid_addrs=0x29957090) at ../sim/freebsd/pf/pf.c:204
204 int n = 0;
(gdb) s
0x28f66150 in _thread_sys_sigprocmask () from
/usr/lib/libc_r.so.4
(gdb) bt
#0 0x28f66150 in _thread_sys_sigprocmask () from
/usr/lib/libc_r.so.4
#1 0x28f2dd4d in _thread_kern_scheduler () from
/usr/lib/libc_r.so.4
#2 0x0 in ?? ()
(gdb) c
Continuing.
Program received signal SIGTRAP, Trace/breakpoint
trap.
pf_open (unit=0x0, ethaddrs=0x299570b0 "",
valid_addrs=0x29957090) at ../sim/freebsd/pf/pf.c:204
204 int n = 0;
(gdb) c
Continuing.
Program received signal SIGTRAP, Trace/breakpoint
trap.
pf_open (unit=0x0, ethaddrs=0x299570b0 "",
valid_addrs=0x29957090) at ../sim/freebsd/pf/pf.c:204
204 int n = 0;
(gdb) c
Continuing.
Program received signal SIGTRAP, Trace/breakpoint
trap.
pf_open (unit=0x0, ethaddrs=0x299570b0 "",
valid_addrs=0x29957090) at ../sim/freebsd/pf/pf.c:204
204 int n = 0;
(gdb) exit
Undefined command: "exit". Try "help".
(gdb) quit
-Kip
__________________________________________________
Do You Yahoo!?
Make a great connection at Yahoo! Personals.
http://personals.yahoo.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011029023746.94559.qmail>