"src/stack/StackAr.d"
> -o"src/stack/StackAr.o" "../src/stack/StackAr.cpp"
> ../src/stack/StackAr.cpp:7: erreur: redefinition of
> ‘Stack::Stack(int)’
> ../src/stack/StackAr.cpp:7: erreur: ‘Stack::Stack(int)’
> previously declared here
> ../src/stack/Sta
r, can the fix for it be backported from gcc 4.x to 3.4.x? I
cannot switch to gcc 4.x for some other reasons. If all this doesn't result
in a solution, is there maybe another way for me to determine which
stackframe is the topmost one? (Should I just compare the function name
with "main"? That'd be a bit dirty, wouldn't it?)
Thanks,
Tim München
On Friday 14 November 2008 10:09:22 Anna Sidera wrote:
> Hello,
>
> The following code works in lcc in windows but it does not work in gcc in
> unix. I think it is memory problem. In lcc there is an option to use more
> temporary memory than the default. Is there something similar in gcc?
>
> #incl
On Tuesday 21 October 2008 20:07:10 `VL wrote:
> Hello, ALL.
>
> I recently started to actively program using C and found that tools like
> ctags or cscope do not work properly for big projects. Quite ofthen they
> can't find function or symbol definition. The problem here is that they
> don't use
On Friday 29 August 2008 23:04:15 you wrote:
> On Fri, Aug 29, 2008 at 2:36 AM, Tim München
>
> <[EMAIL PROTECTED]> wrote:
> > is it somehow possible to also be notified if a function/method is left
> > with a 'throw'? Or, would it be possible to patch gcc l
Hi,
is it somehow possible to also be notified if a function/method is left with
a 'throw'? Or, would it be possible to patch gcc like that? I had a quick
look into function.c but it seems not to be as straight-forward as the
entry/exit instrumentation (What is probably the reason it isn't imp
