Comment 9 for bug 91791

El dom, 18-03-2007 a las 16:23 +0000, Alexander Sack escribió:
> On Sat, Mar 17, 2007 at 12:31:09PM -0000, Hilario J. Montoliu (hjmf) wrote:
> > > Assigning to hjmf to see if he can get a better stacktrace.
> >
> > --- stack trace ---
> > #0 0xffffe410 in ?? ()
> > --- end of stack trace ---
> >
> > I've seen 4-5 reports with this problem (such retrace). Maybe the
> > problem is related to when the report is generated, I mean that the
> > problem is with apport initial process... don't know.
> >
> > This happens only on feisty's reported bugs with just "CoreDump.gz,
> > Dependencies.txt, ProcMaps.txt, ProcStatus.txt and Registers.txt"
> > attached. Are always reports named "[apport] firefox-bin crashed with
> > SIGSEGV" when generated instead of the usual "[apport] firefox-bin
> > crashed with SIGSEGV in __kernel_vsyscall()"
>
> So how does it usually happen that just those files are available? Has
> attaching only those been the default once?

I don't know. Just seen only in those reports.

> In that case it might as
> well just mean: old report -> no proper dbgsym packages -> bad
> retrace?

I don't think so. Reporters package versions seem to be the ones
expected the day the crash was reported (ie firefox 2.0.0.2+1-0ubuntu1)