[Freeciv-Dev] [task #7729] Windows packages for 2.4.0-RC2
Update of task #7729 (project freeciv): Status:None = Done Open/Closed:Open = Closed ___ Follow-up Comment #5: I've announced the Windows packages despite this not being closed, as they seemed to be up and I'm unlikely to have time tomorrow. Hope that wasn't premature in some way. Thanks, all fine. ___ Reply to this item at: http://gna.org/task/?7729 ___ Nachricht gesendet von/durch Gna! http://gna.org/ ___ Freeciv-dev mailing list Freeciv-dev@gna.org https://mail.gna.org/listinfo/freeciv-dev
[Freeciv-Dev] [task #7729] Windows packages for 2.4.0-RC2
Follow-up Comment #3, task #7729 (project freeciv): Another optional change to workflow: do you get map files or debug symbols or something out of your build process? If so, we should arrange to get them uploaded somewhere where Freeciv developers can see them. Whenever we get a Windows-specific crash reported, we Unix-y developers are pretty much in the dark, as we don't have the debug tools. Being able to at least translate a program counter like 0x7c92168b into a source file/line might give us a bit of a clue. If there are any other build entrails that can be combined with Windows post-mortem debug dumps to get stack backtraces and the like, all the better. The binaries contain debug symbols and in case of a crash a backtrace gets saved in 'freeciv-server.RPT' or 'freeciv-gtk2.RPT' in the installation directory already. For some reason the source file/line information is missing in the client report, though. Even 'objdump -dSl' does not show it for the client, but GDB does. So, we'd need at least the output of 'nm' or perhaps 'objdump -d' for the client to interpret the backtrace addresses. And somehow communicate to the users to send the report files together with their bug reports. ___ Reply to this item at: http://gna.org/task/?7729 ___ Nachricht gesendet von/durch Gna! http://gna.org/ ___ Freeciv-dev mailing list Freeciv-dev@gna.org https://mail.gna.org/listinfo/freeciv-dev
[Freeciv-Dev] [task #7729] Windows packages for 2.4.0-RC2
Follow-up Comment #4, task #7729 (project freeciv): I've announced the Windows packages despite this not being closed, as they seemed to be up and I'm unlikely to have time tomorrow. Hope that wasn't premature in some way. The binaries contain debug symbols and in case of a crash a backtrace gets saved in 'freeciv-server.RPT' or 'freeciv-gtk2.RPT' in the installation directory already. [...] For some reason the source file/line information is missing in the client report, though. Even 'objdump -dSl' does not show it for the client, but GDB does. Aha, so perhaps no extra files for us to keep around. I wonder if a MinGW cross-compiler gdb would work for me to access this stuff? Hm. ___ Reply to this item at: http://gna.org/task/?7729 ___ Message sent via/by Gna! http://gna.org/ ___ Freeciv-dev mailing list Freeciv-dev@gna.org https://mail.gna.org/listinfo/freeciv-dev
[Freeciv-Dev] [task #7729] Windows packages for 2.4.0-RC2
URL: http://gna.org/task/?7729 Summary: Windows packages for 2.4.0-RC2 Project: Freeciv Submitted by: jtn Submitted on: Sun Sep 1 12:48:35 2013 Should Start On: Sun Sep 1 00:00:00 2013 Should be Finished on: Sun Sep 8 00:00:00 2013 Category: None Priority: 5 - Normal Status: None Privacy: Public Percent Complete: 0% Assigned to: cproc Open/Closed: Open Discussion Lock: Any Effort: 0.00 Planned Release: ___ Details: Source tarball (.tar.bz2) is now available at download.gna.org. Sorry for the lack of notice and delivery late in the weekend. Your choice whether you address bug #21038 (new Gtk DLLs) with this package or wait for 2.4.1. ___ Reply to this item at: http://gna.org/task/?7729 ___ Message sent via/by Gna! http://gna.org/ ___ Freeciv-dev mailing list Freeciv-dev@gna.org https://mail.gna.org/listinfo/freeciv-dev
[Freeciv-Dev] [task #7729] Windows packages for 2.4.0-RC2
Follow-up Comment #1, task #7729 (project freeciv): Another optional change to workflow: do you get map files or debug symbols or something out of your build process? If so, we should arrange to get them uploaded somewhere where Freeciv developers can see them. Whenever we get a Windows-specific crash reported, we Unix-y developers are pretty much in the dark, as we don't have the debug tools. Being able to at least translate a program counter like 0x7c92168b into a source file/line might give us a bit of a clue. If there are any other build entrails that can be combined with Windows post-mortem debug dumps to get stack backtraces and the like, all the better. ___ Reply to this item at: http://gna.org/task/?7729 ___ Message sent via/by Gna! http://gna.org/ ___ Freeciv-dev mailing list Freeciv-dev@gna.org https://mail.gna.org/listinfo/freeciv-dev
[Freeciv-Dev] [task #7729] Windows packages for 2.4.0-RC2
Follow-up Comment #2, task #7729 (project freeciv): (Just keep what material you have around for now, let's see what there is and we'll work out the best way to distribute it -- I guess a new area on download.gna.org by default.) ___ Reply to this item at: http://gna.org/task/?7729 ___ Message sent via/by Gna! http://gna.org/ ___ Freeciv-dev mailing list Freeciv-dev@gna.org https://mail.gna.org/listinfo/freeciv-dev
