Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "François Chenais" <francois@chenais.net>
To: gdb@sourceware.org
Subject: Re: [OPTERON/x86_64] - can't debug while setting breakpoint
Date: Fri, 20 Feb 2009 09:03:00 -0000	[thread overview]
Message-ID: <499E71D9.4080605@chenais.net> (raw)
In-Reply-To: <49913A3C.9000201@chenais.net>

François Chenais a écrit :
> François Chenais a écrit :
>> Daniel Jacobowitz a écrit :
>>> On Thu, Feb 05, 2009 at 07:49:08PM +0100, François Chenais wrote:
>>>> I've done the test on 5 Amd opteron x86_64 hosts with Cent OS 5.2
>>>>     - The error occurs on 3/5.
>>>
>>> Check that they're all running the same kernel version, check for
>>> kernel updates.  This does not sound like a GDB problem.
>>>
>>
>> They are running the same kernel !
>>
>> Effectively, I don't think it's a gdb problem because the error occurs 
>> for the others debuggers.
>>
>> I have checked the list and the versions of packages installed, the 
>> configuration, all seems identical.
>>
>> What can make the debuggers fail while setting breakpoints ?
>>
>>
> The error occurs on HP 585 G2 not on G1 !:/
> 
> 
Something new.

I tried to build new gdb on this system but it fails during configure.
It fails in the conftest cheking division by zero.

I built the conftest and run gdb on it.
The error occurs when catching SIGFPE signal, gdb is blocked waiting!

   François


  reply	other threads:[~2009-02-20  9:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-05 18:49 [OPTERON/x86_64] - can " François Chenais
2009-02-05 18:57 ` Daniel Jacobowitz
2009-02-05 19:16   ` [OPTERON/x86_64] - can't " François Chenais
2009-02-10  8:26     ` François Chenais
2009-02-20  9:03       ` François Chenais [this message]
2009-02-22 10:46 ` [OPTERON/x86_64] - can " Jan Kratochvil
2009-02-23  7:34   ` François Chenais

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=499E71D9.4080605@chenais.net \
    --to=francois@chenais.net \
    --cc=gdb@sourceware.org \
    /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