Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: "Pierre Muller" <muller@ics.u-strasbg.fr>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] fix win32-nat failure
Date: Thu, 02 Oct 2008 12:12:00 -0000	[thread overview]
Message-ID: <200810021312.02828.pedro@codesourcery.com> (raw)
In-Reply-To: <009a01c9246a$64ece5b0$2ec6b110$@u-strasbg.fr>

On Thursday 02 October 2008 09:39:32, Pierre Muller wrote:

>   Well, in fact, I don't understand this statement,
> after reading it, I suspected that this had to do with the fact that
> I use a lot the 'set new-console on' option,
> but even without this I still get the same assertion failed message,
> so I don't understand why you did not also get it.

Sorry for being vague.  I just meant that this crashes:

 $ ./gdb --quiet ./test.exe
 (gdb) start
 Temporary breakpoint 1 at 0x40107a: file test.c, line 3.
 Starting program: /home/pedro/gdb/baseline/build/gdb/test.exe
 ../../src/gdb/inferior.c:41: internal-error: current_inferior: Assertion `inf' failed.
 A problem internal to GDB has been detected,
 further debugging may prove unreliable.
 Quit this debugging session? (y or n)

But this doesn't:

 $ gdb --args ./gdb ./test.exe
 GNU gdb 6.8.0.20080328-cvs (cygwin-special)
 (top-gdb) run
 Starting program: /home/pedro/gdb/baseline/build/gdb/gdb.exe ./test.exe
...
 (gdb) start
 Temporary breakpoint 1 at 0x40107a: file test.c, line 3.
 Starting program: /home/pedro/gdb/baseline/build/gdb/test.exe
 [New Thread 2196.0x2e0]
 [New Thread 2196.0xbe8]
 
 Temporary breakpoint 1, main () at test.c:3
 3         return 0;
 (gdb)

Because:

 (gdb) i
 (top-gdb) p gdb_has_a_terminal()
 $1 = 0

hence, the crash site is skipped (inflow.c):

 178     void
 179     terminal_init_inferior_with_pgrp (int pgrp)
 180     {
 181       if (gdb_has_a_terminal ())
 182         {

 234     void
 235     terminal_inferior (void)
 236     {
 237       if (gdb_has_a_terminal () && terminal_is_ours
 238           && inferior_ttystate != NULL
 239           && inferior_thisrun_terminal == 0)
 240         {

> OK, let me try this simpler patch out,
> I will send a RFA if that works OK for me.

Thanks!

-- 
Pedro Alves


      parent reply	other threads:[~2008-10-02 12:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-01 12:25 Pierre Muller
2008-10-01 12:50 ` Pedro Alves
2008-10-01 18:10 ` Pedro Alves
2008-10-02  8:41   ` Pierre Muller
2008-10-02 11:58     ` [RFA] " Pierre Muller
2008-10-02 13:02       ` Pedro Alves
2008-10-02 14:22         ` Pierre Muller
2008-10-02 15:25         ` Christopher Faylor
2008-10-02 15:54           ` Pedro Alves
2008-10-02 19:07             ` Christopher Faylor
2008-10-02 12:12     ` Pedro Alves [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=200810021312.02828.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=muller@ics.u-strasbg.fr \
    /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