Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb@sourceware.org
Subject: Re: breakpoint.c:5280: internal-error: expand_line_sal_maybe: Assertion `found' failed.
Date: Mon, 23 Jun 2008 08:22:00 -0000	[thread overview]
Message-ID: <jeej6osgr4.fsf@sykes.suse.de> (raw)
In-Reply-To: <200806230751.44399.vladimir@codesourcery.com> (Vladimir Prus's 	message of "Mon, 23 Jun 2008 07:51:43 +0400")

Vladimir Prus <vladimir@codesourcery.com> writes:

> This should not happen generally -- do you have a small reproducible example?

No, sorry, I saw this while debugging a KDE program.  When I remove the
assertion I get this output (the function starts with an inlined QString
constructor):

(gdb) b 'QFontDatabase::styles(QString const&) const' 
Note: breakpoint 2 also set at pc 0xeaf7078.
Note: breakpoint 2 also set at pc 0xeaf7080.
Note: breakpoint 2 also set at pc 0xeaf7150.
Note: breakpoint 2 also set at pc 0xeaf7080.
Note: breakpoint 2 also set at pc 0xeaf7078.
Note: breakpoint 2 also set at pc 0xeaf7080.
Note: breakpoint 2 also set at pc 0xeaf7150.
Note: breakpoint 2 also set at pc 0xeaf7080.
Note: breakpoint 2 also set at pc 0xeaf7088.
Note: breakpoint 2 also set at pc 0xeaf70a4.
Note: breakpoint 2 also set at pc 0xeaf7080.
Note: breakpoint 2 also set at pc 0xeaf7088.
Note: breakpoint 2 also set at pc 0xeaf7088.
Note: breakpoint 2 also set at pc 0xeaf7088.
Note: breakpoint 2 also set at pc 0xeaf7090.
Note: breakpoint 2 also set at pc 0xeaf7160.
Note: breakpoint 2 also set at pc 0xeaf7080.
Note: breakpoint 2 also set at pc 0xeaf7088.
Note: breakpoint 2 also set at pc 0xeaf719c.
Breakpoint 2 at 0xeaf7078: file ../include/qstring.h, line 842. (41 locations)
(gdb) p 'QFontDatabase::styles(QString const&) const'
$1 = {QStringList (const QFontDatabase * const, 
    const QString &)} 0xed94f50 <QFontDatabase::styles(QString const&) const>
(gdb) i b 2
Num     Type           Disp Enb Address    What
2       breakpoint     keep y   <MULTIPLE> 
2.1                         y     0x0eaf7078 ../include/qstring.h:842
2.2                         y     0x0eaf7080 ../include/qstring.h:842
2.3                         y     0x0eaf7150 ../include/qstring.h:842
2.4                         y     0x0eaf7078 ../include/qstring.h:842
2.5                         y     0x0eaf7080 ../include/qstring.h:842
2.6                         y     0x0eaf7150 ../include/qstring.h:842
2.7                         y     0x0eaf7080 ../include/qstring.h:842
2.8                         y     0x0eaf7088 ../include/qstring.h:842
2.9                         y     0x0eaf70a4 ../include/qstring.h:842
2.10                        y     0x0eaf718c ../include/qstring.h:842
2.11                        y     0x0eaf7194 ../include/qstring.h:842
2.12                        y     0x0eaf71b0 ../include/qstring.h:842
2.13                        y     0x0eaf730c ../include/qstring.h:842
2.14                        y     0x0eaf7078 ../include/qstring.h:842
2.15                        y     0x0eaf7080 ../include/qstring.h:842
2.16                        y     0x0eaf7150 ../include/qstring.h:842
2.17                        y     0x0eaf7080 ../include/qstring.h:842
2.18                        y     0x0eaf7088 ../include/qstring.h:842
2.19                        y     0x0eaf70a4 ../include/qstring.h:842
2.20                        y     0x0eaf7264 ../include/qstring.h:842
2.21                        y     0x0eaf7080 ../include/qstring.h:842
2.22                        y     0x0eaf7088 ../include/qstring.h:842
2.23                        y     0x0eaf719c ../include/qstring.h:842
2.24                        y     0x0eaf7088 ../include/qstring.h:842
2.25                        y     0x0eaf7088 ../include/qstring.h:842
2.26                        y     0x0eaf7090 ../include/qstring.h:842
2.27                        y     0x0eaf7090 ../include/qstring.h:842
2.28                        y     0x0eaf7160 ../include/qstring.h:842
2.29                        y     0x0eaf7160 ../include/qstring.h:842
2.30                        y     0x0eaf7080 ../include/qstring.h:842
2.31                        y     0x0eaf7088 ../include/qstring.h:842
2.32                        y     0x0eaf719c ../include/qstring.h:842
2.33                        y     0x0eaf707c ../include/qstring.h:842
2.34                        y     0x0eaf7084 ../include/qstring.h:842
2.35                        y     0x0eaf71bc ../include/qstring.h:842
2.36                        y     0x0eaf70ac ../include/qstring.h:842
2.37                        y     0x0eaf70c4 ../include/qstring.h:842
2.38                        y     0x0eaf7228 ../include/qstring.h:842
2.39                        y     0x0eaf737c ../include/qstring.h:842
2.40                        y     0x0ed94fbc in QFontDatabase::styles(QString const&) const at ../include/qstring.h:842
2.41                        y     0x0ed951f0 in QFontDatabase::styles(QString const&) const at ../include/qstring.h:842

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."


      reply	other threads:[~2008-06-23  8:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-22 23:46 Andreas Schwab
2008-06-23  3:52 ` Vladimir Prus
2008-06-23  8:22   ` Andreas Schwab [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jeej6osgr4.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=gdb@sourceware.org \
    --cc=vladimir@codesourcery.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox