This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: dmalloc and __throw
- To: briareos at lokigames dot com
- Subject: Re: dmalloc and __throw
- From: "Martin v. Loewis" <martin at mira dot isdn dot cs dot tu-berlin dot de>
- Date: Tue, 26 Oct 1999 01:04:32 +0200
- CC: gcc-bugs at gcc dot gnu dot org
- References: <19991025135536.F28646@namaste.lokigames-lan.com>
> While I would love to contribute test cases, I haven't been able to
> build any that fail and the code in question is not open. Mostly, I
> just need to know whether I'm on crack, my binutils are fubarred, I
> need to look harder for problems dmalloc wouldn't catch, or if there
> really may be nasty problems inside of egcs that I'm exposing with
> this 500,000 line project.
I guess part of your problem is that __throw cannot be properly
debugged, right? If that is the case, you should recompile libgcc.a
with -g. It is compiled with -g1 by default (according to the
Makefile, "so that -g1 will be tested" - I never found that very
useful).
Hopefully, with proper line and variable info, you can find the
problem.
Good luck,
Martin