Bug#306537: firefox: Stacktrace from the crash

2006-04-22 Thread Luke Reeves
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Here's an uncorrupted stack trace from the last crash: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -103712 (LWP 5136)] 0xb7f218ce in JSLL_MinInt () from /usr/lib/firefox/libmozjs.so #0 0xb7f218ce in JSLL_MinInt () fr

Bug#306537: firefox: Stacktrace from the crash

2006-04-20 Thread Luke Reeves
Sure, I'll set it up and submit the error once (or if) it occurs again. Luke On Thu, Apr 20, 2006 at 04:12:05PM -0400, Justin Pryzby wrote: > On Tue, Apr 18, 2006 at 10:22:50PM -0400, Luke Reeves wrote: > > Package: firefox > > Version: 1.5.dfsg+1.5.0.1-4 > > Followup-For: Bug #306537 > >

Bug#306537: firefox: Stacktrace from the crash

2006-04-20 Thread Justin Pryzby
On Tue, Apr 18, 2006 at 10:22:50PM -0400, Luke Reeves wrote: > Package: firefox > Version: 1.5.dfsg+1.5.0.1-4 > Followup-For: Bug #306537 > > I managed to capture a stack trace. Here it is for > what it's worth: > > Program received signal SIGPIPE, Broken pipe. Sigpipe means writing to a pipe wi

Bug#306537: firefox: Stacktrace from the crash

2006-04-18 Thread Luke Reeves
Package: firefox Version: 1.5.dfsg+1.5.0.1-4 Followup-For: Bug #306537 I managed to capture a stack trace. Here it is for what it's worth: Program received signal SIGPIPE, Broken pipe. [Switching to Thread -1222562896 (LWP 4571)] 0xb7dbf83e in send () from /lib/tls/libpthread.so.0 (gdb) (gdb) b