** Branch linked: lp:debian/polipo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1168593
Title:
Occasional Assertion Failure causing crash in dispose_chunk in chunk.c
To manage notifications about
This bug was fixed in the package polipo - 1.1.1-1
---
polipo (1.1.1-1) unstable; urgency=medium
* release newest upstream version 1.1.1. Closes: #746750
- use regerror to improve error reporting. Closes: #585766
- correct return value from processObject in error case.
Sorry for the delayed response.
It's been a while since I did this, but how I debugged this was adding
-g -rdynamic to the build options to insure that GCC would not strip
symbols needed to backtrace, as well as using nostrib in the
DEB_BUILD_OPTIONS so that debian's build script thing wouldn't
I'm currently packaging the latest upstream release and I would love to
incorporate your work on packaging the debugging information. I'd
appreciate your input.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ping
** Changed in: polipo (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1168593
Title:
Occasional Assertion Failure causing crash in dispose_chunk
Sean, thank you for reporting back.
If you can help me compile the package with symbol tables for debugging,
I'll gladly upload that (and the latest fixes).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Well, the crashes are now much, MUCH, rarer, I just got one. (First time
since I got Rolf's branch of it).
Sadly, as it was compiled without symbol tables, the stack trace was
pretty much useless. Should I rebuild with symbols so I can get a useful
stacktrace?
--
You received this bug
For those of you who would like to test my wip packages before I upload
them to Debian, you can get them for precise (and later) from my stable
PPA: https://launchpad.net/~r0lf/+archive/stable
Please kindly let me know if you can reproduce the issue with the latest
package.
** Changed in: polipo
Alright, recompiled with libsegfault as one of the included libraries
(forcing better line numbers in dumps), and got the line number of the
assertion failure, chunk.c:398:dispose_chunk.
Line numbers for the whole stack still aren't showing up (ugh), but I
can see that it is happening when it is
Alright, recompiled with libsegfault as one of the included libraries
(forcing better line numbers in dumps), and got the line number of the
assertion failure, chunk.c:398:dispose_chunk.
Line numbers for the whole stack still aren't showing up (ugh), but I
can see that it is happening when it is
Also, when you are not compiling with debug flags, are the asserts
disabled? If so, the derefence of that null pointer could explain why
some people see segfaults instead of assertion failures.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I will also try to see if I can upload a patch implementing the
suggested workaround for chunk.c, until the true reason for the bug is
found.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1168593
12 matches
Mail list logo
