public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: jakacki@cidc.com.cn
To: gcc-gnats@gcc.gnu.org
Subject: debug/3352: extern/inline combination in try/catch causes wrong lineinfo for all symbols in file
Date: Thu, 21 Jun 2001 18:46:00 -0000 [thread overview]
Message-ID: <20010622013811.31326.qmail@sourceware.cygnus.com> (raw)
>Number: 3352
>Category: debug
>Synopsis: extern/inline combination in try/catch causes wrong lineinfo for all symbols in file
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Thu Jun 21 18:46:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: Grzegorz Jakacki <jakacki@cidc.com.cn>
>Release: gcc version 2.95.2 19991024 (release) , GNU nm 2.9.1
>Organization:
>Environment:
sparc-sun-solaris2.6
>Description:
When there is extern function call in 'try' and inlined
function is called 'catch', and this construct appears in
the last function definition in the source file, all the
symbols in the file get the lineinfo of the inlined
function.
The bug was also present in nightly x86 GNU/Linux
build on 2001-06-20, gcc-3_0-branch (CodeSourcery).
>How-To-Repeat:
$ gcc -c -g inlined_catch_debuginfo_bug.cc
$ nm -l inlined_catch_debuginfo_bug.o | grep main
000000e0 t Letext /home/jakacki/projects/partition/systemc_release/src/gcc-bug/inlined_catch_debuginfo_bug.cc:11
00000000 ? __EXCEPTION_TABLE__ /home/jakacki/projects/partition/systemc_release/src/gcc-bug/inlined_catch_debuginfo_bug.cc:11
00000000 ? __FRAME_BEGIN__ /home/jakacki/projects/partition/systemc_release/src/gcc-bug/inlined_catch_debuginfo_bug.cc:11
U __cp_pop_exception /home/jakacki/projects/partition/systemc_release/src/gcc-bug/inlined_catch_debuginfo_bug.cc:11
U __eh_rtime_match /home/jakacki/projects/partition/systemc_release/src/gcc-bug/inlined_catch_debuginfo_bug.cc:11
U __rtti_user /home/jakacki/projects/partition/systemc_release/src/gcc-bug/inlined_catch_debuginfo_bug.cc:11
U __start_cp_handler /home/jakacki/projects/partition/systemc_release/src/gcc-bug/inlined_catch_debuginfo_bug.cc:11
00000000 W __tf9exception /home/jakacki/projects/partition/systemc_release/src/gcc-bug/inlined_catch_debuginfo_bug.cc:11
U __throw /home/jakacki/projects/partition/systemc_release/src/gcc-bug/inlined_catch_debuginfo_bug.cc:11
00000008 C __ti9exception
U external__Fv /home/jakacki/projects/partition/systemc_release/src/gcc-bug/inlined_catch_debuginfo_bug.cc:11
00000000 W inlined__Fv /home/jakacki/projects/partition/systemc_release/src/gcc-bug/inlined_catch_debuginfo_bug.cc:11
00000000 T main /home/jakacki/projects/partition/systemc_release/src/gcc-bug/inlined_catch_debuginfo_bug.cc:11
U terminate__Fv /home/jakacki/projects/partition/systemc_release/src/gcc-bug/inlined_catch_debuginfo_bug.cc:11
$ cat inlined_catch_debuginfo_bug.cc
//
// compile with 'gcc -c -g'
// (gcc version 2.95.2 19991024 (release))
//
// and make 'nm -l'; the line number of 'main' is 11 not 15 */
// GNU nm 2.9.1
class exception {
};
inline void inlined() {} /* line 11 */
extern void external();
int main(int argc, char* argv[]) /* line 15 */
{
try
{
external();
}
catch(const exception &x)
{
inlined();
}
}
$
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2001-06-21 18:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-21 18:46 jakacki [this message]
2001-12-18 14:23 dberlin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010622013811.31326.qmail@sourceware.cygnus.com \
--to=jakacki@cidc.com.cn \
--cc=gcc-gnats@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).