We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
Hi,
Thanks for the information.
There is a chance that the dbgsym packages do
change what is loaded at runtime, as so change
the stack and memory layout.
I'll mark the bug as Incomplete, as it does reflect
the status better, i.e. there is a bug for you, but
there isn't enough information to know
On Sat, Mar 29, 2008 at 11:13 AM, James Westby
<[EMAIL PROTECTED]> wrote:
> It's my understanding that the dbgsym packages just put the symbols
> in a location for gdb to access when it needs them, so they don't
> have any effect on the program running as normal. However I may
> be wrong about
On Sat, 2008-03-29 at 14:17 +, lcampagn wrote:
> I've seen it before--my understanding is that adding the debugging
> symbols changes the memory signature in the stack. So for example,
> what used to corrupt some crucial memory might now just overwrite text
> in a debugging symbol. Alternativel
I've seen it before--my understanding is that adding the debugging
symbols changes the memory signature in the stack. So for example,
what used to corrupt some crucial memory might now just overwrite text
in a debugging symbol. Alternatively, the presence of debuggibg
symbols might slightly alter t
On Sat, 2008-03-29 at 02:07 +, lcampagn wrote:
> I can't reproduce the bug with the dbgsym package, I left it running
> for 45 minutes or so with no problem. After removing dbgsym, the
> segfault is back again after ~5 minutes.
>
Ok, that's quite unusual, are you sure no other package was
rem
I can't reproduce the bug with the dbgsym package, I left it running
for 45 minutes or so with no problem. After removing dbgsym, the
segfault is back again after ~5 minutes.
*shrug* At least I've got a workaround.
On Sun, Mar 2, 2008 at 8:05 PM, James Westby <[EMAIL PROTECTED]> wrote:
> Hi,
>
>
Hi,
Could you install some dbgsym packages and get a new backtrace
which should give some more information please?
https://wiki.ubuntu.com/DebuggingProgramCrash
shows some information on doing this.
Thanks,
James
--
segfault in hydrogen after ~5minutes of use
https://bugs.launchpad.net/bugs/
