pidgin seg fault when xmpp server sends NULL conversation

[chris_c]

Binary package hint: pidgin

I see some console messages about NULL conversations then it seg faults

[dforsi (daniele-forsi)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. 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 problem.

Please also state which version of Ubuntu and of pidgin you are using.

[chris_c (c-camacho)]

I am using Jaunty with pidgin 2.5.4

I installed the debug info but was unable to get a meaningful backtrace

(gdb) run
Starting program: /usr/bin/pidgin
[Thread debugging using libthread_db enabled]
[New Thread 0x7f86184127d0 (LWP 6156)]
[New Thread 0x7f85fa041950 (LWP 6175)]
[New Thread 0x7f85f8d62950 (LWP 6176)]
[New Thread 0x7f85f3fff950 (LWP 6177)]
[New Thread 0x7f85f37fe950 (LWP 6178)]
[Thread 0x7f85f37fe950 (LWP 6178) exited]
[Thread 0x7f85f3fff950 (LWP 6177) exited]
[Thread 0x7f85f8d62950 (LWP 6176) exited]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f85fa041950 (LWP 6175)]
0x00007f85f8927140 in ?? ()
(gdb) bt
#0 0x00007f85f8927140 in ?? ()
#1 0x00007f8614fbf459 in start_thread () from /lib/libpthread.so.0
#2 0x00007f8614d2bfcd in clone () from /lib/libc.so.6
#3 0x0000000000000000 in ?? ()
(gdb)

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

 * Is this reproducible?
 * If so, what specific steps should we take to recreate this bug?
 * Could you try on jaunty now?

 This will help us to find and resolve the problem.

[chris_c (c-camacho)]

* Is this reproducible?

only if a server sends null messages (jabber.org was doing quite a lot for a while, you would have to set up a local server for testing)

* If so, what specific steps should we take to recreate this bug?

send null messages to a pidgin client

* Could you try on jaunty now?

I no longer use jaunty

[darkrain42 (darkrain42)]

What do you mean by "Null" message? What is the XML (check the ebug log -- `pidgin -d`) that you receive that makes it crash?

[chris_c (c-camacho)]

the client reported a Null message error before the seg fault,
where might I find the "ebug" log?

darkrain42 wrote:
> What do you mean by "Null" message? What is the XML (check the ebug log
> -- `pidgin -d`) that you receive that makes it crash?
>
>

--
Disclaimer:
By sending an email to ANY of my addresses you are agreeing that:

   1. I am by definition, "the intended recipient"

   2. All information in the email is mine to do with as I see fit and
make such financial profit, political mileage, or good joke as it lends
itself to. In particular, I may quote it where I please.

   3. I may take the contents as representing the views of your company.

   4. This overrides any disclaimer or statement of confidentiality that
may be included on your message.

[darkrain42 (darkrain42)]

A typo, it should read 'debug'.

Start pidgin from a terminal and pass it the -d command-line option. You can optionally pipe it to a file (`pidgin -d > debug.log`) and open the file afterward. You probably don't need to attach the full log but the last 20 lines or so before it crashes should be sufficient.

[chris_c (c-camacho)]

No server currently is sending malformed packets

I do not have time to set one up locally

This could possibly be exploited as a security issue
(its certainly effective DoS)

I've upgraded since no idea if this is still a bug mine...

darkrain42 wrote:
> A typo, it should read 'debug'.
>
> Start pidgin from a terminal and pass it the -d command-line option. You
> can optionally pipe it to a file (`pidgin -d > debug.log`) and open the
> file afterward. You probably don't need to attach the full log but the
> last 20 lines or so before it crashes should be sufficient.
>
>

--
Disclaimer:
By sending an email to ANY of my addresses you are agreeing that:

   1. I am by definition, "the intended recipient"

   2. All information in the email is mine to do with as I see fit and
make such financial profit, political mileage, or good joke as it lends
itself to. In particular, I may quote it where I please.

   3. I may take the contents as representing the views of your company.

   4. This overrides any disclaimer or statement of confidentiality that
may be included on your message.

[Vish (vish)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.
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".