On Wed, Feb 25, 2009 at 05:10:45PM +0000, Richard W.M. Jones wrote: > On Wed, Feb 25, 2009 at 01:53:23PM +0000, Daniel P. Berrange wrote: > > Last time we tried, a cross compiled GDB crashed & burned. So unless someone > > can demonstrate a usuable WINE/Win32 debugger that can use the gcc generated > > debugging info, then we should not build with -g, nor create -debuginfo > > sub-RPMs. > > > > The exception being the base toolchain that is natively compiled should of > > course have debuginfo as normal. > > According to this: > > http://sourceforge.net/mailarchive/message.php?msg_name=8278b1b0902240411i58f4b5d0y7c8a69604dfe5ce4%40mail.gmail.com > > Windows has its own native debugging format (*.PDB) that GCC/GDB (or > perhaps MinGW) doesn't support anyway.
So not useful in the general case for debugging under Windows / using the MicroSoft debugger, but I guess the question is whether there is none-the-less a more limited case in which GCC debuginfo is useful ? eg if cross-compiling and then debugging the app under Wine using GDB, would minggw-XXX-debuginfo RPMs still be useful to have ? If so, then that could be justification for providing them [1]. Daniel [1] Assuming we could also produce a working GDB build for use in Wine :-) -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| _______________________________________________ fedora-mingw mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/fedora-mingw
