crash upon canceling of further campaigns

Thanks for your bug. I'll see what I can find out.

Debian has 0.8.21-3 but I can't see a fix for this bug, or a report of it either.

The latest version upstream is the same as in edgy - 0.8.21

This bug doesn't occur in upstream's bug tracker. (http://savannah.nongnu.org/bugs/?group=glob2)

We need to see if we can reproduce and then send upstream.

It would be useful if you followed the instructions in https://wiki.ubuntu.com/DebuggingProgramCrash to install a debug version of glob2. This will enable you to produce more detailed crash files.

Caroline Ford wrote:
> Debian has 0.8.21-3 but I can't see a fix for this bug, or a report of
> it either.
>
> The latest version upstream is the same as in edgy - 0.8.21
>
> This bug doesn't occur in upstream's bug tracker.
> (http://savannah.nongnu.org/bugs/?group=glob2)
>
> We need to see if we can reproduce and then send upstream.
I can reproduce this: win campaign six, and when the dialog comes up
asking if one wishes to continue, hit cancel.

>
> It would be useful if you followed the instructions in
> https://wiki.ubuntu.com/DebuggingProgramCrash to install a debug version
> of glob2. This will enable you to produce more detailed crash files.
>
I've attached the result of following those must excellent instructions.

--

System Administrator for Cave Wall Arts (\ /)

"A craftsman is one who understands his tools and his materials and uses
them with skill and honesty" -Thomas Hibben, 1933

GNU gdb 6.4.90-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu"...(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".

(gdb) handle SIG33 pass nostop noprint
Signal Stop Print Pass to program Description
SIG33 No No Yes Real-time event 33
(gdb) set pagination 0
(gdb) run
Starting program: /usr/games/glob2
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47714191531584 (LWP 23137)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
Settings::load("preferences.txt") : error, can't open file.
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[New Thread 1082132816 (LWP 23144)]
(no debugging symbols found)
[New Thread 1090525520 (LWP 23145)]
[New Thread 1098918224 (LWP 23146)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 47714191531584 (LWP 23137)]
0x0000000000567cb7 in std::char_traits<char>::eq...

I canceled, going on further in the campaign. That caused Glob2 to crash.

I confirm this bug. Same just happened here.

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu - the Intrepid Ibex.

If you need a fix for the bug in previous versions of Ubuntu, please follow the instructions for "How to request new packages" at https://help.ubuntu.com/community/UbuntuBackports#request-new-packages