From owner-freebsd-hackers Mon Mar 19 12:46: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mw2.texas.net (mw2.texas.net [206.127.30.12]) by hub.freebsd.org (Postfix) with ESMTP id 99D6A37B726 for ; Mon, 19 Mar 2001 12:45:59 -0800 (PST) (envelope-from hackthis@texas.net) Received: from hackthis (tcnet07-051.sat.texas.net [209.99.119.177]) by mw2.texas.net (8.11.1/8.11.1) with SMTP id f2JKjuU01727 for ; Mon, 19 Mar 2001 14:45:57 -0600 (CST) Message-ID: <005401c0b0b8$1e7f3ca0$6346a8c0@hackthis> From: "hackthis" To: Subject: gcc and exceptions and frame.c Date: Mon, 19 Mar 2001 15:03:57 -0600 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0051_01C0B085.D2B83380" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0051_01C0B085.D2B83380 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Freebsd-hackers: Been trying to debug a program of mine and keep running into these = errors. I was wondering if there is a problem with exceptions and gccor with freebsd in = general?? I think frame.c has to do with exceptions. What do you all think about all those cannot access memory errors. Thanks for any help, c.r.g. # gdb /a.out ./a.out.core 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"... Core was generated by `a.out'. Program terminated with signal 6, Abort trap. Cannot access memory at address 0x280f0e3c. #0 0x2815c530 in ?? ()Cannot access memory at address 0x280f0e3c. (gdb) bt #0 0x2815c530 in ?? ()Cannot access memory at address 0x280f0e3c. #2 0x2816a55f in ?? ()Cannot access memory at address 0x280f0e3c. #3 0x28169fc3 in ?? ()Cannot access memory at address 0x280f0e3c. #4 0x28169d71 in ?? ()Cannot access memory at address 0x280f0e3c. #5 0xbfbfdfcc in ?? ()Cannot access memory at address 0x280f0e3c. #6 0x80a3aa7 in frame_init (ob=3D0x8119cc8) at ./frame.c:626 626 ./frame.c: No such file or directory. Current language: auto; currently c #7 0x80a3afa in find_fde (pc=3D0x80a2e46) at ./frame.c:626 626 in ./frame.c #8 0x80a3ffc in __frame_state_for (pc_target=3D0x80a2e46, = state_in=3D0x819cbc0) at ./frame.c:627 627 in ./frame.c #9 0x80a2e57 in __throw ()Cannot access memory at address 0x280f0e3c. #10 0x80a4337 in __builtin_new (sz=3D356) Cannot access memory at address 0x280f0e3c. Current language: auto; currently c++ #16 0x28139b3a in ?? ()Cannot access memory at address 0x280f0e3c. #17 0x0 in ?? ()Cannot access memory at address 0x280f0e3c. Initial frame selected; you cannot go up. (gdb) info threads * 1 process 8373 0x0 in ?? ()Cannot access memory at address = 0x280f0e3c. warning: Couldn't restore frame in current thread, at frame 0 0x0 in ?? ()Cannot access memory at address 0x280f0e3c. compiling with=20 $ g++295 -v Reading specs from = /usr/local/lib/gcc-lib/i386-portbld-freebsd3.4/2.95.2/specs gcc version 2.95.2 19991024 (release) ------=_NextPart_000_0051_01C0B085.D2B83380 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Freebsd-hackers:

Been trying to debug a program of mine = and keep=20 running into these errors. I was wondering

if there is a problem with exceptions = and gccor=20 with freebsd in general?? I think frame.c has to do with=20 exceptions.

What do you all think about all those = cannot access=20 memory errors.

Thanks for any help,

c.r.g.

# gdb /a.out ./a.out.core
GNU gdb=20 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free = software,=20 covered by the GNU General Public License, and you are
welcome to = change it=20 and/or distribute copies of it under certain conditions.
Type "show = copying"=20 to see the conditions.
There is absolutely no warranty for GDB. = Type=20 "show warranty" for details.
This GDB was configured as=20 "i386-unknown-freebsd"...
Core was generated by `a.out'.
Program=20 terminated with signal 6, Abort trap.
Cannot access memory at address = 0x280f0e3c.
#0 0x2815c530 in ?? ()Cannot access memory at = address=20 0x280f0e3c.
(gdb) bt
#0 0x2815c530 in ?? ()Cannot access = memory at=20 address 0x280f0e3c.
#2 0x2816a55f in ?? ()Cannot access memory = at=20 address 0x280f0e3c.
#3 0x28169fc3 in ?? ()Cannot access memory = at=20 address 0x280f0e3c.
#4 0x28169d71 in ?? ()Cannot access memory = at=20 address 0x280f0e3c.
#5 0xbfbfdfcc in ?? ()Cannot access memory = at=20 address 0x280f0e3c.
#6 0x80a3aa7 in frame_init (ob=3D0x8119cc8) = at=20 ./frame.c:626
626     ./frame.c: No such file or=20 directory.
Current language: auto; currently c
#7 = 0x80a3afa in=20 find_fde (pc=3D0x80a2e46) at = ./frame.c:626
626     in=20 ./frame.c
#8 0x80a3ffc in __frame_state_for = (pc_target=3D0x80a2e46,=20 state_in=3D0x819cbc0)
    at=20 ./frame.c:627
627     in ./frame.c
#9 = 0x80a2e57=20 in __throw ()Cannot access memory at address 0x280f0e3c.
#10 = 0x80a4337 in=20 __builtin_new (sz=3D356)
Cannot access memory at address = 0x280f0e3c.
Current=20 language: auto; currently c++
#16 0x28139b3a in ?? ()Cannot = access=20 memory at address 0x280f0e3c.
#17 0x0 in ?? ()Cannot access memory at = address=20 0x280f0e3c.
Initial frame selected; you cannot go up.

(gdb) = info=20 threads
* 1 process 8373 0x0 in ?? ()Cannot access memory at = address=20 0x280f0e3c.
warning: Couldn't restore frame in current thread, at = frame=20 0
0x0 in ?? ()Cannot access memory at address=20 0x280f0e3c.

compiling with
$ g++295 -v
Reading = specs from=20 /usr/local/lib/gcc-lib/i386-portbld-freebsd3.4/2.95.2/specs
gcc = version=20 2.95.2 19991024 (release)

------=_NextPart_000_0051_01C0B085.D2B83380-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message