I have a single-threaded executable that has a number of debug-print
routines that can be called interactively in the debugger to display
data structures to stderr. Something has changed in gdb/gcc/Cygwin
during the last year or so (I don't update my installation very often)
so that when I call on
On Jun 20 09:29, William M. (Mike) Miller wrote:
> I have a single-threaded executable that has a number of debug-print
> routines that can be called interactively in the debugger to display
> data structures to stderr. Something has changed in gdb/gcc/Cygwin
> during the last year or so (I don't
On Sat, Jun 20, 2015 at 2:47 PM, Corinna Vinschen
wrote:
> On Jun 20 09:29, William M. (Mike) Miller wrote:
>> I have a single-threaded executable that has a number of debug-print
>> routines that can be called interactively in the debugger to display
>> data structures to stderr. Something has c
On 6/20/2015 4:02 PM, William M. (Mike) Miller wrote:
Thanks for the reply. My concern, however, isn't that new threads are
being created; it's that when gdb does this, it sets the state of all
threads, including my main thread, to "(running)" so that I can't
single-step through my program any m
On Sat, Jun 20, 2015 at 4:42 PM, Ken Brown wrote:
> On 6/20/2015 4:02 PM, William M. (Mike) Miller wrote:
>>
>> Thanks for the reply. My concern, however, isn't that new threads are
>> being created; it's that when gdb does this, it sets the state of all
>> threads, including my main thread, to "
On 6/20/2015 4:51 PM, William M. (Mike) Miller wrote:
On Sat, Jun 20, 2015 at 4:42 PM, Ken Brown wrote:
On 6/20/2015 4:02 PM, William M. (Mike) Miller wrote:
Thanks for the reply. My concern, however, isn't that new threads are
being created; it's that when gdb does this, it sets the state o
On Sun, Jun 21, 2015 at 3:29 PM, Ken Brown wrote:
> On 6/20/2015 4:51 PM, William M. (Mike) Miller wrote:
>>
>> On Sat, Jun 20, 2015 at 4:42 PM, Ken Brown wrote:
>>>
>>> On 6/20/2015 4:02 PM, William M. (Mike) Miller wrote:
Thanks for the reply. My concern, however, isn't that new
People who can reproduce this problem and can also build their own GDB
are encouraged to try the patch posted here:
https://sourceware.org/ml/gdb/2015-06/msg00071.html
and report whether it solves the problem on Cygwin. (I already
verified that the native MinGW debugging is fixed by that patch
On Wed, Jun 24, 2015 at 10:33 AM, Eli Zaretskii wrote:
> People who can reproduce this problem and can also build their own GDB
> are encouraged to try the patch posted here:
>
> https://sourceware.org/ml/gdb/2015-06/msg00071.html
>
> and report whether it solves the problem on Cygwin. (I alrea
On Wed, Jun 24, 2015 at 10:33 AM, Eli Zaretskii wrote:
> People who can reproduce this problem and can also build their own GDB
> are encouraged to try the patch posted here:
>
> https://sourceware.org/ml/gdb/2015-06/msg00071.html
>
> and report whether it solves the problem on Cygwin. (I alrea
10 matches
Mail list logo
