On Mon, May 08, 2006 at 03:55:01AM -0700, Brian Dessent wrote:
>Brian Dessent wrote:
>>I expect that after 1.5.20 is out the door an updated gdb binary
>>package will happen,
>
> will _eventually_ happen
>
>...as in, I'm not the gdb maintainer and don't pretend to presume any
>kind of implied s
On 05/08/2006, clayne wrote:
Is there any form of profiling, etc. enabled in the snap builds?
Snapshots have separately downloadable debug symbols, if that would help in
this case...
--
Larry Hall http://www.rfk.com
RFK Partners, Inc. (508) 89
One thing about this 4-27 snap, and I noticed it with 4-03 as well (which I
reverted from a while ago) is that disk i/o appears to be ridiculously slow
in comparison to 1.5.19. In rough estimation, I'd have to say a 50% reduction
in I/O throughput. I notice it while working with mass updating of f
Brian Dessent wrote:
> I expect that after 1.5.20 is out the door an updated gdb binary package
> will happen,
will _eventually_ happen
...as in, I'm not the gdb maintainer and don't pretend to presume any
kind of implied schedule.
--
Unsubscribe info: http://cygwin.com/ml/#unsubsc
[EMAIL PROTECTED] wrote:
> Thanks Brian, much better. The issue was that I could not find any reference
> to the problem ever being fixed - just a lot of threads where people were
> ending with "yea you gotta hit continue - it sucks."
Right. It was reported often, and because of that there was a
On Mon, May 08, 2006 at 02:44:37AM -0700, [EMAIL PROTECTED] wrote:
>
> On Mon, May 08, 2006 at 02:01:00AM -0700, Brian Dessent wrote:
> >
> > Rather than work-arounds, why not just use a recent build of gdb that
> > doesn't suffer from this problem? The issue was fixed in CVS earlier
> > this ye
On Mon, May 08, 2006 at 02:01:00AM -0700, Brian Dessent wrote:
>
> Rather than work-arounds, why not just use a recent build of gdb that
> doesn't suffer from this problem? The issue was fixed in CVS earlier
> this year. But do note that it requires functionality not present in
> Cygwin 1.5.19,
[EMAIL PROTECTED] wrote:
> Someone throw me a bone here, please.
Rather than work-arounds, why not just use a recent build of gdb that
doesn't suffer from this problem? The issue was fixed in CVS earlier
this year. But do note that it requires functionality not present in
Cygwin 1.5.19, so you'
Alright, I'm aware of the "check for invalid memory region and throw
exception" issue present when debugging pthread applications under gdb
and that the actual segfault is innocuous. However, the following solutions:
1. "handle SIGSEGV nostop"
"handle SIGTRAP nostop"
2. (hit continue on every
9 matches
Mail list logo
