[Spice-devel] [PATCH] common: add backtrace via gstack
Alon Levy
alevy at redhat.com
Mon Jul 18 02:47:55 PDT 2011
On Mon, Jul 18, 2011 at 11:13:50AM +0200, Christophe Fergeau wrote:
> On Mon, Jul 18, 2011 at 11:57:47AM +0300, Alon Levy wrote:
> > On Mon, Jul 18, 2011 at 10:13:27AM +0200, Christophe Fergeau wrote:
> > > What use case do you have in mind for this? Is it meant for use during
> > > development when something asserts but we forgot to run it in gdb? Or do
> > > you want to get more backtraces from crashes in bugzilla? I'm asking
> > > because /usr/bin/gstack comes in the gdb package here, which is not likely
> > > to be installed on "users" boxes. glibc also has backtrace(3) and
> > > backtrace_symbols(3), but they are explicitly documented as GNU extensions.
> >
> > Both I guess. Ok, so this fails the second use case. I can do both -
> > compile backtrack support in if it is available (there must be some
> > define I can use)
>
> Or this can be checked for in configure.ac
>
>
> > and do gstack first if available, otherwise (if
> > compiled in) glibc's backtrace.
>
> Yep, though for now we can just go with the gstack based trace, and add the
> backtrace() code later if it's really needed.
>
> Christophe
I'll take that as an ack.
> _______________________________________________
> Spice-devel mailing list
> Spice-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/spice-devel
More information about the Spice-devel
mailing list