From: Kai Tietz <ktietz70@googlemail.com>
To: Kai Tietz <ktietz70@googlemail.com>,
Chris Sutcliffe <ir0nh34d@gmail.com>,
gdb@sourceware.org
Subject: Re: [gdb-7.1] 10 days to branching...
Date: Wed, 03 Feb 2010 08:20:00 -0000 [thread overview]
Message-ID: <90baa01f1002030019n531a35der5c36161c78373f97@mail.gmail.com> (raw)
In-Reply-To: <20100202224349.GA31505@ednor.casa.cgf.cx>
2010/2/2 Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>:
> On Tue, Feb 02, 2010 at 05:02:11PM +0100, Kai Tietz wrote:
>>2010/2/2 Chris Sutcliffe <ir0nh34d@gmail.com>:
>>>> I don't know - I had never heard of anyone doing this kind of build
>>>> before: ?From what I can tell, you are building a MinGW debugger using
>>>> a cygwin compiler. ?If no one answered, it's probably because no one
>>>> has anything to say (including: "that ought to work"). ?Have you tried
>>>> using a MinGW compiler instead?
>>>
>>> For the mingw-w64 build, I did indeed build from within Cygwin using
>>> the mingw-w64 cross compiling toolchain provided by the mingw-w64
>>> project. ?For the MinGW32 binary I built it using MSYS and the MinGW
>>> compiler. ?In both cases this is the method I used to the build the
>>> 7.0.1 binary.
>>
>>Yes, I can confirm that buiding on a cygwin host by a valid
>>cross-compiler is working nicely. I justed tried, and for me it still
>>works. Possibly an issue about passed configure options?
>>
>>Just one point I found today. The new break-point handling seems to
>>have problems in certain ways for me (at least on win32 versions). I
>>get in case of setting breakpoints in Obj-C always the assertation
>>'set_raw_breakpoint: Assertation sal.pspace != NULL' failed'. This is
>>new and is somehow related to recent enhancements to breakpoint
>>handling.
>
> I don't see anything like this when setting breakpoints in a c++
> app. I'm not familiar with objective-C but I believe I managed to
> build a simple hello world app. I set a breakpoint in main with
> no problem.
>
> This is with a i686-cygwin gdb built on linux.
>
> cgf
>
Hallo Christopher,
well for basic Object-C apps, I don't see the issue, too. For C and
C++ I couldn't reproduce this. This seems to happen on setting of
breakpoint on Object-C methods in shared object.
I tried two different ways to set breakpoint. First variant is before
starting (as pending breakpoint). This works a long as the DLL isn't
loaded. As soon as it is, the gdb gives the above mentioned
asseration. Second variant is, starting application and stopping it by
Crtl-C, setting breakpoint. Here the problem is shown directly.
I can provide the application I have (it is an about 50MB binary) and
owned by the company I am working, but it seems that in such scenario
the pspace remains NULL.
Thanks for you trying,
Kai
--
| (\_/) This is Bunny. Copy and paste
| (='.'=) Bunny into your signature to help
| (")_(") him gain world domination
next prev parent reply other threads:[~2010-02-03 8:20 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 [this message]
2010-02-03 19:39 ` Christopher Faylor
2010-02-05 22:02 ` Tom Tromey
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=90baa01f1002030019n531a35der5c36161c78373f97@mail.gmail.com \
--to=ktietz70@googlemail.com \
--cc=gdb@sourceware.org \
--cc=ir0nh34d@gmail.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