Just tried to have some fun but toycars 0.3.10 are crashing when after I finish Timed Race - i.e. after finish all 4 rounds. 1. Start New Game and choose "Timed Race". 2. Choose "Oval" track. 3. Choose "New Human Player" and any car, then "New AI Player" and any car. Then Done. 4. Finish all 4 rounds. (Crash) The output is below. I've recompiled with C[XX]FLAGS="-O1 -pipe -ggdb" and FEATURES="nostrip" but I do not know where the toycars functions names in the backtrace are. I'll add emerge --info as attachment. $ toycars Default Data Dir: /usr/share/games/toycars Changing to directory: /usr/share/games/toycars User data dir: /home/hs/.toycars/ 0 joysticks were found. The names of the joysticks are: toycars Arrows: steering and throttle for player 1 adws: steering and throttle for player 2 f: aproximate seconds per frame c: change camera mode tab: in Hot Potato Mode - print debug info for player holding the bomb p: pause Esc: quit Exception caught File: main.cpp Function: chooseTrack Line: 1717 Message: xml user tracklist file not found Ignoring exception... Setting up animation... Exception caught File: main.cpp Function: chooseToyCar Line: 552 Message: xml user carslist file not found Ignoring exception... Exception caught File: main.cpp Function: chooseToyCar Line: 552 Message: xml user carslist file not found Ignoring exception... successfully created tileset from tilesets/default/ done all lights done minimap done setup successfully created track from tracks/Oval/ Loading all textures... Number of joysticks available: 0 *** buffer overflow detected ***: toycars terminated ======= Backtrace: ========= /lib/libc.so.6(__fortify_fail+0x37)[0x7ffb327e5297] /lib/libc.so.6[0x7ffb327e3070] /lib/libc.so.6[0x7ffb327e2369] /lib/libc.so.6(__printf_fp+0x1183)[0x7ffb327494e3] /lib/libc.so.6(_IO_vfprintf+0x1dae)[0x7ffb32744b3e] /lib/libc.so.6(__vsprintf_chk+0x9d)[0x7ffb327e240d] /lib/libc.so.6(__sprintf_chk+0x80)[0x7ffb327e2350] toycars[0x404745] toycars[0x405c23] toycars[0x404d13] toycars[0x407070] toycars[0x40e974] toycars[0x40f60e] toycars[0x4143cb] /lib/libc.so.6(__libc_start_main+0xe6)[0x7ffb3271e5c6] toycars(_ZNSt8ios_base4InitD1Ev+0x39)[0x404189] ======= Memory map: ======== 00400000-00440000 r-xp 00000000 08:06 71702 /usr/games/bin/toycars 0063f000-00640000 r--p 0003f000 08:06 71702 /usr/games/bin/toycars 00640000-00641000 rw-p 00040000 08:06 71702 /usr/games/bin/toycars 00641000-00642000 rw-p 00000000 00:00 0 019a5000-0307b000 rw-p 00000000 00:00 0 [heap] 4142d000-414ab000 rw-p 00000000 00:0a 478 /dev/zero 4162c000-4162e000 rwxp 00000000 00:0a 478 /dev/zero 7ffb2af88000-7ffb2af89000 ---p 00000000 00:00 0 7ffb2af89000-7ffb2b789000 rwxp 00000000 00:00 0 7ffb2b789000-7ffb2b78a000 ---p 00000000 00:00 0 7ffb2b78a000-7ffb2bf8a000 rwxp 00000000 00:00 0 7ffb2bf8a000-7ffb2bf8b000 ---p 00000000 00:00 0 7ffb2bf8b000-7ffb2c78b000 rwxp 00000000 00:00 0 7ffb2c78b000-7ffb2c8eb000 rw-p 00000000 00:00 0 7ffb2c8f9000-7ffb2cb13000 rw-p 00000000 00:00 0 7ffb2cb13000-7ffb2cc13000 rw-s 7bc0b000 00:0a 10523 /dev/nvidia0 7ffb2cc13000-7ffb2cc14000 rw-s f4c02000 00:0a 10523 /dev/nvidia0 7ffb2cc14000-7ffb2cd14000 rw-s 47959000 00:0a 10523 /dev/nvidia0 7ffb2cd14000-7ffb2d214000 rw-s d0000000 00:0a 10523 /dev/nvidia0 7ffb2d214000-7ffb2d21c000 r-xp 00000000 08:06 9263886 /lib64/librt-2.9.so 7ffb2d21c000-7ffb2d41b000 ---p 00008000 08:06 9263886 /lib64/librt-2.9.so 7ffb2d41b000-7ffb2d41c000 r--p 00007000 08:06 9263886 /lib64/librt-2.9.so 7ffb2d41c000-7ffb2d41d000 rw-p 00008000 08:06 9263886 /lib64/librt-2.9.so 7ffb2d41d000-7ffb2d4e3000 r-xp 00000000 08:06 2461798 /usr/lib64/libasound.so.2.0.0 7ffb2d4e3000-7ffb2d6e2000 ---p 000c6000 08:06 2461798 /usr/lib64/libasound.so.2.0.0 7ffb2d6e2000-7ffb2d6e8000 r--p 000c5000 08:06 2461798 /usr/lib64/libasound.so.2.0.0 7ffb2d6e8000-7ffb2d6ea000 rw-p 000cb000 08:06 2461798 /usr/lib64/libasound.so.2.0.0 7ffb2d6ea000-7ffb2d6ef000 r-xp 00000000 08:06 5660919 /usr/lib64/libXfixes.so.3.1.0 7ffb2d6ef000-7ffb2d8ee000 ---p 00005000 08:06 5660919 /usr/lib64/libXfixes.so.3.1.0 7ffb2d8ee000-7ffb2d8ef000 r--p 00004000 08:06 5660919 /usr/lib64/libXfixes.so.3.1.0 7ffb2d8ef000-7ffb2d8f0000 rw-p 00005000 08:06 5660919 /usr/lib64/libXfixes.so.3.1.0 7ffb2d8f0000-7ffb2d8f9000 r-xp 00000000 08:06 9752822 /usr/lib64/libXcursor.so.1.0.2 7ffb2d8f9000-7ffb2daf8000 ---p 00009000 08:06 9752822 /usr/lib64/libXcursor.so.1.0.2 7ffb2daf8000-7ffb2daf9000 r--p 00008000 08:06 9752822 /usr/lib64/libXcursor.so.1.0.2 7ffb2daf9000-7ffb2dafa000 rw-p 00009000 08:06 9752822 /usr/lib64/libXcursor.so.1.0.2 7ffb2dafa000-7ffb2db47000 rw-p 00000000 00:00 0 7ffb2db7b000-7ffb2de79000 r--p 00000000 08:06 5658735 /usr/lib64/locale/locale-archive 7ffb2de79000-7ffb2de81000 r-xp 00000000 08:06 5032060 /usr/lib64/libXrandr.so.2.2.0 7ffb2de81000-7ffb2e080000 ---p 00008000 08:06 5032060 /usr/lib64/libXrandr.so.2.2.0 7ffb2e080000-7ffb2e081000 r--p 00007000 08:06 5032060 /usr/lib64/libXrandr.so.2.2.0 7ffb2e081000-7ffb2e082000 rw-p 00008000 08:06 5032060 /usr/lib64/libXrandr.so.2.2.0 7ffb2e082000-7ffb2e08b000 r-xp 00000000 08:06 3018839 /usr/lib64/libXrender.so.1.3.0 7ffb2e08b000-7ffb2e28a000 ---p 00009000 08:06 3018839 /usr/lib64/libXrender.so.1.3.0 7ffb2e28a000-7ffb2e28b000 r--p 00008000 08:06 3018839 /usr/lib64/libXrender.so.1.3.0 7ffb2e28b000-7ffb2e28c000 rw-p 00009000 08:06 3018839 /usr/lib64/libXrender.so.1.3.0 7ffb2e28c000-7ffb2e28f000 r-xp 00000000 08:06 2306241 /lib64/libuuid.so.1.3.0 7ffb2e28f000-7ffb2e48e000 ---p 00003000 08:06 2306241 /lib64/libuuid.so.1.3.0 7ffb2e48e000-7ffb2e48f000 r--p 00002000 08:06 2306241 /lib64/libuuid.so.1.3.0 7ffb2e48f000-7ffb2e490000 rw-p 00003000 08:06 2306241 /lib64/libuuid.so.1.3.0 7ffb2e490000-7ffb2e4a5000 r-xp 00000000 08:06 8230928 /lib64/libz.so.1.2.3 7ffb2e4a5000-7ffb2e6a4000 ---p 00015000 08:06 8230928 /lib64/libz.so.1.2.3 7ffb2e6a4000-7ffb2e6a5000 r--p 00014000 08:06 8230928 /lib64/libz.so.1.2.3 7ffb2e6a5000-7ffb2e6a6000 rw-p 00015000 08:06 8230928 /lib64/libz.so.1.2.3 7ffb2e6a6000-7ffb2e6af000 r-xp 00000000 08:06 5011489 /usr/lib64/libXi.so.6.0.0 7ffb2e6af000-7ffb2e8ae000 ---p 00009000 08:06 5011489 /usr/lib64/libXi.so.6.0.0 7ffb2e8ae000-7ffb2e8af000 r--p 00008000 08:06 5011489 /usr/lib64/libXi.so.6.0.0 7ffb2e8af000-7ffb2e8b0000 rw-p 00009000 08:06 5011489 /usr/lib64/libXi.so.6.0.0 7ffb2e8b0000-7ffb2e90b000 r-xp 00000000 08:06 626585 /usr/lib64/libXt.so.6.0.0 7ffb2e90b000-7ffb2eb0b000 ---p 0005b000 08:06 626585 /usr/lib64/libXt.so.6.0.0 7ffb2eb0b000-7ffb2eb0c000 r--p 0005b000 08:06 626585 /usr/lib64/libXt.so.6.0.0 7ffb2eb0c000-7ffb2eb11000 rw-p 0005c000 08:06 626585 /usr/lib64/libXt.so.6.0.0 7ffb2eb11000-7ffb2eb12000 rw-p 00000000 00:00 0 7ffb2eb12000-7ffb2eb29000 r-xp 00000000 08:06 2441443 /usr/lib64/libXmu.so.6.2.0 7ffb2eb29000-7ffb2ed29000 ---p 00017000 08:06 2441443 /usr/lib64/libXmu.so.6.2.0 7ffb2ed29000-7ffb2ed2a000 r--p 00017000 08:06 2441443 /usr/lib64/libXmu.so.6.2.0 7ffb2ed2a000-7ffb2ed2b000 rw-p 00018000 08:06 2441443 /usr/lib64/libXmu.so.6.2.0 7ffb2ed2b000-7ffb2ed41000 r-xp 00000000 08:06 5497927 /usr/lib64/libICE.so.6.3.0 7ffb2ed41000-7ffb2ef40000 ---p 00016000 08:06 5497927 /usr/lib64/libICE.so.6.3.0Aborted
Created attachment 225589 [details] emerge --info
Are you still suffering this problem?
Yes I do.
I cannot see toycars packaged in any major distribution and, then, I couldn't find any patch that could fix this issue. Maybe you could try to report this problem to upstream: http://sourceforge.net/tracker/?group_id=143140&atid=759873 But maybe this is your problem: http://sourceforge.net/tracker/?func=detail&aid=2953934&group_id=143140&atid=759873 and looks like upstream is dead... in that case, if nobody is able to fix it, maybe this should be treecleaned :/
It seems that it is the same issue. I have added a comment there pointing to this bug report.
commit 75701fb0f45f07e4529aa03f5817a36c8dc98262 Author: Michał Górny <mgorny@gentoo.org> AuthorDate: Sun Jun 26 17:14:21 2016 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: Sun Jun 26 17:14:21 2016 games-sports/toycars: Remove last rited packages
5 Reasons For Finishing Coats On Your Brownies Packaging Box Brownies packaging box can be a beautiful tool that helps your brand or product grow in popularity if it is done well. It may also become a waste of money and resources if it is not designed with thought and care. Introduction To Brownies Packaging Design Brownies packaging design comprises many things that need to be considered for it to achieve its goal. These can range from choosing the right material, printing, colors, and even its shape. The choice of the colors will depend on the number of sides that are included in your brownies packaging box. Even though some boxes can be rectangular or square in shape, most packaging for brownies is designed with different sides. That is to ensure that it has a stable structure to prevent the content from being damaged during transport. At the end of the day, the design of brownie boxes packaging is dependent on the brand and the product and what it is used for. Furthermore, the target audience plays a vital role in its design, which means that it may be designed differently for different target groups. Thus, creating different packaging boxes for different target groups can be beneficial. One of the best ways to change the design of your brownie boxes packaging is by using finishing coats. What Are Finishing Coats? Finishing coats are added to the brownies boxes packaging as a decoration that will make your product look professional and attractive. It does not change the quality of its design; instead, it is an extra touch that you can use to enhance how it looks before it goes out for sale or distribution. They are thin layers of paint that are attached to the brownies boxes packaging. While they look similar to stickers, they are not removable. That means once it is stuck on the box, there is no turning back. With this in mind, these finishing coats can determine how unique your design is. For instance, the finishing coat can make your design more visible on retail shelves, so it can be seen by everyone What Are They Different Types Of Finishing Coats? There are different types of finishing coats available, which include the following: • Gloss Finishing Coats • Matte Finishing Coats • Varnish Finishing Coats • Soft-Touch Finishing Coat Let's study these options briefly. Gloss Finishing Coats The glossy finish is one of the most common finishing coats that you can use. It makes your design look shiny and attractive, which will make your product stand out on retail shelves. This finish also protects your box from scratches and moisture such as water and oil. Packaging brownies with a glossy finishing coat will make your products more noticeable on retail shelves, which you want as a creator or manufacturer. Matte Finishing Coats The matte finish is almost always used to create subtle designs that do not stand out too much, such as brownies packaging. That means if you desire your design not to stand out, this is the best finishing coat that you can choose. However, matte finishes are not good at protecting your brownies packaging design from moisture and scratches, which means they might lose their quality over time. Varnish Finishing Coats Instead of gloss or matte, some people prefer to use varnishes as a finishing coat. They are not as shiny as the gloss or as subtle as matte finishes, which means they can be used to create bold designs that stand out. Varnish also provides a good level of protection against moisture and scratches, so your design will remain intact for longer without being affected by external factors Soft-Touch Finishing Coats This modern finishing coat can be used to create a tactile feel that is soft and almost velvety to the touch. That's why it is good for packaging brownies with a luxury design, which can be used to impress your audience. Now you know about the basics of finishing coats and some popular options. Let's study the 5 main reasons you should always opt for finishing coats in your brownies packaging box designs. 5 Reasons To Use Finishing Coats In Your Brownies Packaging Boxes Designs Here are the five reasons to use finishing coats in your brownies packaging box designs: 1. Enhances Visibility One of the main benefits of using a finishing coat is that it can enhance your design's visibility on retail shelves. That means it will make people notice your product more easily and make it more valuable. 2. Protection Against Scratches Finishing coats protect your brownies packaging designs from scratches and moisture such as water and oil. That means it will ensure your design remains intact for longer without being affected by outside factors. 3. Prevents Your Brownies Packaging From Warping Another reason to use finishing coats is that it prevents your brownie boxes packaging from warping. That means your package will stay intact for longer, which is great news if you want your products to reach the shelves in good condition. 4. Enables Personalization Using finishing coats enables you to make your design more personal. That is because of the wide range of different coatings available, which means you can choose the best option for your brownies box packaging designs. 5. Help You Change Design Easily Imagine if you want a make an entire catalog of flavored brownies. However, you don't want to change the packaging design for every flavor. In that case, it will be ideal to use finishing coats that don't damage your original design. You can introduce a completely different aesthetic and complement various flavors by just changing the finishing coat. To Sum It All Up This blog has provided you with 5 reasons why finishing coats are a good idea for your brownies packaging box designs. The coating helps enhance visibility, prevent warping and ensure that your design stays intact due to protection against moisture and scratches. It also enables you to change the design easily by just switching the finishing coat. So go out there and start using finishing coats to enhance the design of your brownies packaging box. Website: https://packagingbee.com/custom-printed-cbd-brownies-boxes/
