Bug#3007: segfault in strcpy is not debuggable
David Engel writes ("Re: Bug#3007: segfault in strcpy is not debuggable"):
> > > It has to do with libc.so being compiled with -fomit-frame-pointer.
> > > You can use the static libc.a if you really need a stack trace.
> > > Unless you are going to make a case that -fomit-frame-pointer should
> > > never be used in Debian, I'm going to close this bug report.
> > Ah, I see. In the days of a.out this was solved by making GCC link
> > things statically if you linked them with -g. Would it not be
> > possible to provide a separate libc_g5.so or something which isn't
> > compiled in this way ?
> If you use -ggdb, gcc will attempt to link in libg instead of libc.
> However, I didn't include libg in libc5-dev since it's huge. I can
> either add a symlink in libc5-dev from libg.a to libc.a or I can make
> a new package libc5-dbg (?) with libg.a. If I did the latter, I would
> probably also move the profiling libc from libc5-dev to the new
Right, fine. I like the idea of a separate package.
I didn't realise the situation was the same as for the a.out libc (I
thought there was some marvellous new scheme that meant you didn't
need to link statically with a special libc).