pidgin crashed with SIGSEGV in malloc()

[Ignacio Nieto]

Binary package hint: pidgin

-

ProblemType: Crash
Architecture: i386
Date: Mon Nov 2 11:42:29 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/pidgin
NonfreeKernelModules: nvidia
Package: pidgin 1:2.6.2-1ubuntu7
ProcCmdline: pidgin
ProcEnviron:
 LANG=es_AR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0xcfd448: mov %edx,0x8(%ecx)
 PC (0x00cfd448) ok
 source "%edx" ok
 destination "0x8(%ecx)" (0x00000044) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: pidgin
StacktraceTop:
 ?? () from /lib/tls/i686/cmov/libc.so.6
 malloc () from /lib/tls/i686/cmov/libc.so.6
 g_malloc () from /lib/libglib-2.0.so.0
 g_strsplit () from /lib/libglib-2.0.so.0
 msn_command_from_string ()
Title: pidgin crashed with SIGSEGV in malloc()
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[J. Austin Rodriguez (jeanaustinr)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures

At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).
Thanks!

[Victor Vargas (kamus)]

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 the current status, under the Status column, and change the Status back to "New". Thanks again!