Processed: your mail

2012-12-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 696320 important Bug #696320 [libstdc++6-4.4-dbg] Reading symbols from /usr/lib/libstdc++.so.6...(no debugging symbols found)...done Severity set to 'important' from 'grave' > severity 696854 important Bug #696854 [libstdc++6-4.7-dbg] Re

Bug#696320:

2012-12-28 Thread Mathieu Malaterre
severity 696320 important severity 696854 important thanks downgrading severity since there are workarounds (using LD_LIBRARY_PATH) -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://list

Bug#696854:

2012-12-28 Thread Mathieu Malaterre
Here is the output for libstdc++6-4.7-dbg: (debian sid): $ gdb bla (gdb) set verbose on (gdb) r Starting program: /tmp/bla Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/ld-linux-x86-64.so.2 Reading symbols from system-supplied DSO

Processed: your mail

2012-12-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > clone 696320 -1 Bug #696320 [libstdc++6-4.4-dbg] Reading symbols from /usr/lib/libstdc++.so.6...(no debugging symbols found)...done Bug 696320 cloned as bug 696854 > reassign -1 libstdc++6-4.7-dbg Bug #696854 [libstdc++6-4.4-dbg] Reading symbols

Bug#696320: Reading symbols from /usr/lib/libstdc++.so.6...(no debugging symbols found)...done

2012-12-28 Thread Mathieu Malaterre
On Thu, Dec 20, 2012 at 9:31 PM, Andrey Rahmatullin wrote: > > /usr/lib/x86_64-linux-gnu/debug/libstdc++.so.6 instead of > /usr/lib/debug/usr/lib/x86_64-linux-gnu/libstdc++.so.6 sounds wrong to me. > Also, if it's indeed wrong then other versions of libstdc++ are affected > too. I am not clear wh