On Thu, 2009-02-05 at 18:58 +, Richard Seguin wrote:
> Thank you for the valgrind log, it indeed is quite helpful. The only
> thing left would be the typical system information. Typically I would
> have asked you to re-report this bug using apport, which provides needed
> system information
Thank you for the valgrind log, it indeed is quite helpful. The only
thing left would be the typical system information. Typically I would
have asked you to re-report this bug using apport, which provides needed
system information automatically. In your case could you run the
following commands
I will attach the valgrind log as requested. It clearly demonstrates
the memory leak I talked about but no segfault.
** Attachment added: "valgrind log -- memory leak, no segfault"
http://launchpadlibrarian.net/22013572/valgrind.log.gz
--
segfault
https://bugs.launchpad.net/bugs/321258
You r
On Fri, 2009-01-30 at 11:30 +, Richard Seguin wrote:
> More specifically, in that link there will be another to obtain a
> valgrind log, please attach that as a separate attachment
Well, yeah. There is definitely a memory leak in pidgin:
PID USER PR NI VIRT RES SHR S %CPU %MEM
More specifically, in that link there will be another to obtain a
valgrind log, please attach that as a separate attachment
--
segfault
https://bugs.launchpad.net/bugs/321258
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
It seems that one of my posts didn't quite make it through, sorry about
that...
Please try to obtain a backtrace following the instructions at
http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace
(as an attachment) to the bug report. This will greatly help us in
tracking down your
Same here. Working fine today, Jan. 28, 2009 until I rebooted after
today's routine auto-updates to Hearty Kubuntu.
I have no idea what additional information you need, if you can refer me
to a site *detailing how to get you* additional information that you
need I'll be glad to help.
Here's what
* The status of this report has been changed to incomplete and has been
assigned a priority as a member of bug-control has elected to triage
this issue with your assistance. Once enough information has been
gathered the status will be set to "confirmed" then "triaged" if deemed
necessary.
Thank yo
** Attachment added: "stack trace"
http://launchpadlibrarian.net/21626496/foo
--
segfault
https://bugs.launchpad.net/bugs/321258
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.co
