Thread View: gnu.gdb.bug
2 messages
2 total messages
Started by Doug Schmidt
Sun, 15 Jan 1989 01:35
gdb 3.0 gets infinite loop on sun 3
Author: Doug Schmidt
Date: Sun, 15 Jan 1989 01:35
Date: Sun, 15 Jan 1989 01:35
55 lines
2601 bytes
2601 bytes
Hi,
The following transcription demonstrates gdb 3.0 going into
an infinite loop:
----------------------------------------
Script started on Sat Jan 14 17:31:31 1989
[~ ] [/cd/ua/schmidt]
[pompe] [1]..: gdb /usr/public/lib/gcc/gcc-cc1
Reading symbol data from /usr/public/lib/gcc/gcc-cc1...done.
(gdb) b start
Breakpoint 1 at 0x2020
(gdb) r
Starting program: /usr/public/lib/gcc/gcc-cc1
Bpt 1, 0x2020 in start ()
(gdb) where
#0 0x2020 in start ()
#1 0x1 in ?? ()
#2 0x551bc in recog_1 (x0=(rtx) 0x8359c, insn=(rtx) 0x700b6000) (insn-recog.c line 105)
#3 0x670c23cb in end ()
#4 0x551bc in recog_1 (x0=(rtx) 0x8359c, insn=(rtx) 0x700b6000) (insn-recog.c line 105)
#5 0x670c23cb in end ()
#6 0x551bc in recog_1 (x0=(rtx) 0x8359c, insn=(rtx) 0x700b6000) (insn-recog.c line 105)
#7 0x670c23cb in end ()
#8 0x551bc in recog_1 (x0=(rtx) 0x8359c, insn=(rtx) 0x700b6000) (insn-recog.c line 105)
#9 0x670c23cb in end ()
#10 0x551bc in recog_1 (x0=(rtx) 0x8359c, insn=(rtx) 0x700b6000) (insn-recog.c line 105)
#11 0x670c23cb in end ()
#12 0x551bc in recog_1 (x0=(rtx) 0x8359c, insn=(rtx) 0x700b6000) (insn-recog.c line 105)
#13 0x670c23cb in end ()
#14 0x551bc in recog_1 (x0=(rtx) 0x8359c, insn=(rtx) 0x700b6000) (insn-recog.c line 105)
#15 0x670c23cb in end ()
#16 0x551bc in recog_1 (x0=(rtx) 0x8359c, insn=(rtx) 0x700b6000) (insn-recog.c line 105)
#17 0x670c23cb in end ()
#18 0x551bc in recog_1 (x0=(rtx) 0x8359c, insn=(rtx) 0x700b6000) (insn-recog.c line 105)
#19 0x670c23cb in end ()
[ remainder of infinite loop omitted for brevity ]
(gdb) quit
The program is running. Quit anyway? (y or n) y
[~ ] [/cd/ua/schmidt]
[pompe] [2]..: exit
[~ ] [/cd/ua/schmidt]
exit
script done on Sat Jan 14 17:32:12 1989
----------------------------------------
Doug
--
schmidt@ics.uci.edu (ARPA) | Per me si va nella citta' dolente.
office: (714) 856-4043 | Per me si va nell'eterno dolore.
| Per me si va tra la perduta gente.
| Lasciate ogni speranza o voi ch'entrate.
using gdb
Author: Doug Schmidt
Date: Sun, 15 Jan 1989 02:37
Date: Sun, 15 Jan 1989 02:37
20 lines
1309 bytes
1309 bytes
Hi,
Could someone please tell me if there is any way to emulate the dbx
``trace'' feature with gdb 3.0? For example, I'd like to print out
some diagnostics (e.g., parameter list, etc.) every time a particular
function is called, and to have the debugger just keep running
automatically after each output.
Another useful ability would be to have the debugger *stop*
everytime it entered any and every function. Is this also possible
using the conditional break feature?
thanks,
Doug Schmidt
--
schmidt@ics.uci.edu (ARPA) | Per me si va nella citta' dolente.
office: (714) 856-4043 | Per me si va nell'eterno dolore.
| Per me si va tra la perduta gente.
| Lasciate ogni speranza o voi ch'entrate.
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads