Could this be the same bug as:
https://bugzilla.novell.com/show_bug.cgi?id=390722
and
https://bugs.launchpad.net/ubuntu/hardy/+source/gdb/+bug/111869
?
(with patch available)
James
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On Sun, Jun 22, 2008 at 07:30:59PM -0400, James Y Knight wrote:
Could this be the same bug as:
https://bugzilla.novell.com/show_bug.cgi?id=390722
and
https://bugs.launchpad.net/ubuntu/hardy/+source/gdb/+bug/111869
?
(with patch available)
No, it's not related.
--
Daniel Jacobowitz
On Thu, Jun 12, 2008 at 06:19:35PM +0200, Pierre Habouzit wrote:
Is a shared library involved?
No, the symbol is local, visibility hidden.
Normally, when this happens, there is a symbol in the ELF symbol
table (.symtab) for the hidden symbol. That symbol is missing in your
case.
I don't
On Fri, Jun 13, 2008 at 06:04:53PM +, Daniel Jacobowitz wrote:
On Thu, Jun 12, 2008 at 06:19:35PM +0200, Pierre Habouzit wrote:
Is a shared library involved?
No, the symbol is local, visibility hidden.
Normally, when this happens, there is a symbol in the ELF symbol
table
Package: gdb
Version: 6.8-3
Severity: grave
Justification: renders package unusable
Since the 6.8 releases, gdb totally fails to detect stack frames
correctly, whereas the lenny version (6.7.1-2 atm) works fine. My
architecture is amd64, but I've seen the same issues on i386 FWIW.
The code
severity 485955 normal
thanks
On Thu, Jun 12, 2008 at 05:41:02PM +0200, Pierre Habouzit wrote:
Since the 6.8 releases, gdb totally fails to detect stack frames
correctly, whereas the lenny version (6.7.1-2 atm) works fine. My
architecture is amd64, but I've seen the same issues on i386 FWIW.
On Thu, Jun 12, 2008 at 03:58:18PM +, Daniel Jacobowitz wrote:
severity 485955 normal
thanks
On Thu, Jun 12, 2008 at 05:41:02PM +0200, Pierre Habouzit wrote:
Since the 6.8 releases, gdb totally fails to detect stack frames
correctly, whereas the lenny version (6.7.1-2 atm) works
On Thu, Jun 12, 2008 at 06:11:28PM +0200, Pierre Habouzit wrote:
#0 sms_emi_ack_5X (out=0x1b1dc88, msg=0x7fff637d97e0) at
lib-inet/sms-emi.c:230
#1 0x00404973 in ?? ()
With gdb from etch:
(gdb) bt
#0 sms_emi_ack_5X (out=0x110dc88, msg=0x7fff73230240) at
lib-inet/sms-emi.c:230
On Thu, Jun 12, 2008 at 04:13:39PM +, Daniel Jacobowitz wrote:
On Thu, Jun 12, 2008 at 06:11:28PM +0200, Pierre Habouzit wrote:
#0 sms_emi_ack_5X (out=0x1b1dc88, msg=0x7fff637d97e0) at
lib-inet/sms-emi.c:230
#1 0x00404973 in ?? ()
With gdb from etch:
(gdb) bt
#0
On Thu, Jun 12, 2008 at 04:19:35PM +, Pierre Habouzit wrote:
On Thu, Jun 12, 2008 at 04:13:39PM +, Daniel Jacobowitz wrote:
On Thu, Jun 12, 2008 at 06:11:28PM +0200, Pierre Habouzit wrote:
#0 sms_emi_ack_5X (out=0x1b1dc88, msg=0x7fff637d97e0) at
lib-inet/sms-emi.c:230
#1
On Thu, Jun 12, 2008 at 06:19:35PM +0200, Pierre Habouzit wrote:
sid:
(gdb) list smsc_emi_on_query
No line number known for smsc_emi_on_query.
(gdb) b smsc_emi_on_query
Breakpoint 1 at 0x404520
The debug readers were not able to parse this function's debug info.
Is there any
On Thu, Jun 12, 2008 at 04:47:02PM +, Pierre Habouzit wrote:
Also, the testsuite is still running but I already saw those failures:
Running
/home/madcoder/debian/tmp/gdb-6.8/gdb/testsuite/gdb.base/break.exp ...
FAIL: gdb.base/break.exp: breakpoint at start of multi line while
On Thu, Jun 12, 2008 at 06:47:03PM +0200, Pierre Habouzit wrote:
(gdb) b smsc_emi_on_query
During symbol reading, DW_AT_name missing from DW_TAG_base_type.
During symbol reading, unsupported tag: 'DW_TAG_const_type'.
Breakpoint 1 at 0x404520
These complaints are not relevant
On Thu, Jun 12, 2008 at 05:00:18PM +, Daniel Jacobowitz wrote:
On Thu, Jun 12, 2008 at 06:47:03PM +0200, Pierre Habouzit wrote:
(gdb) b smsc_emi_on_query
During symbol reading, DW_AT_name missing from DW_TAG_base_type.
During symbol reading, unsupported tag:
14 matches
Mail list logo
