From: Tom Tromey <tromey@redhat.com>
To: Kai Tietz <ktietz70@googlemail.com>
Cc: Chris Sutcliffe <ir0nh34d@gmail.com>, gdb@sourceware.org
Subject: Re: [gdb-7.1] 10 days to branching...
Date: Fri, 05 Feb 2010 22:02:00 -0000 [thread overview]
Message-ID: <m33a1fcpe9.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20100203193934.GA12020@ednor.casa.cgf.cx> (Christopher Faylor's message of "Wed, 3 Feb 2010 14:39:34 -0500")
>>>>> "cgf" == Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org> writes:
cgf> Any possibility that you can confirm whether this is a windows-only
cgf> problem?
cgf> I think the only way to do that is to provide a test case.
It is not Windows-specific. I reproduced it with a c++ program on my
x86 F11 box.
The program comes from PR 9032:
#include <stdio.h>
class InstSelection {
public:
InstSelection(double d) {
}
public:
virtual ~InstSelection(void);
void dump(void);
};
InstSelection::~InstSelection(void)
{
}
void InstSelection::dump(void)
{
printf("InstSelection::dump here\n");
}
int main(void)
{
InstSelection *is = new InstSelection(17.0);
is->dump();
delete is; is = 0;
return 0;
}
I compiled it with the system g++, then ran CVS head gdb on the
executable. Finally:
(gdb) b InstSelection::InstSelection
../../src/gdb/breakpoint.c:4962: internal-error: set_raw_breakpoint: Assertion `sal.pspace != NULL' failed.
The sal causing the problem in set_raw_breakpoint:
(top-gdb) p sal
$10 = {
pspace = 0x0,
symtab = 0x0,
section = 0x0,
line = 0,
pc = 0,
end = 0,
explicit_pc = 0,
explicit_line = 0
}
That seems odd.
Tom
next prev parent reply other threads:[~2010-02-05 22:02 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-01 8:20 Joel Brobecker
2010-02-01 16:09 ` Chris Sutcliffe
2010-02-02 4:17 ` Joel Brobecker
2010-02-02 12:35 ` Chris Sutcliffe
2010-02-02 16:02 ` Kai Tietz
2010-02-02 16:27 ` Christopher Faylor
2010-02-02 16:46 ` Chris Sutcliffe
2010-02-02 18:46 ` Kai Tietz
2010-02-02 22:44 ` Christopher Faylor
2010-02-03 8:20 ` Kai Tietz
2010-02-03 19:39 ` Christopher Faylor
2010-02-05 22:02 ` Tom Tromey [this message]
2010-02-06 4:55 ` Joel Brobecker
2010-02-06 16:26 ` Pedro Alves
2010-02-06 18:41 ` Matt Rice
2010-02-11 18:25 ` Tom Tromey
[not found] ` <20100212051007.GI2919@adacore.com>
2010-02-12 6:16 ` Joel Brobecker
2010-02-12 11:37 ` Pedro Alves
2010-02-12 11:47 ` Pedro Alves
2010-02-12 17:13 ` Tom Tromey
2010-02-12 19:01 ` Pedro Alves
2010-02-12 20:11 ` Michael Snyder
2010-02-03 8:15 ` André Pönitz
2010-02-03 12:01 ` Chris Sutcliffe
2010-02-12 1:24 ` Stan Shebs
2010-02-12 5:11 ` Joel Brobecker
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=m33a1fcpe9.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sourceware.org \
--cc=ir0nh34d@gmail.com \
--cc=ktietz70@googlemail.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