This is the mail archive of the archer@sourceware.org mailing list for the Archer project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [python] Implement gdb.search_memory.

From: Jan Kratochvil <jan dot kratochvil at redhat dot com>
To: Thiago Jung Bauermann <bauerman at br dot ibm dot com>
Cc: Phil Muldoon <pmuldoon at redhat dot com>, archer ml <archer at sourceware dot org>
Date: Thu, 26 Feb 2009 03:46:29 +0100
Subject: Re: [python] Implement gdb.search_memory.
References: <1235167411.1028.33.camel@localhost.localdomain> <20090223192753.GA31461@host0.dyn.jankratochvil.net> <49A3AA37.6000302@redhat.com> <1235613711.27609.36.camel@localhost.localdomain>

On Thu, 26 Feb 2009 03:01:51 +0100, Thiago Jung Bauermann wrote:
> The problem seems to be that our compilers have their nitpicking levels
> set to different values. Perhaps someone could tell me how I can make my
> compiler behave like Fedora's? I'm using:

Assuming you still run 32bit.  When I put there `long' it is compatible to be
passed as `Py_ssize_t *'.


> > > Could you please check-in something backward/forward compatible?
> 
> This is not the issue here, it seems. But do we want to enforce
> backward/forward compatibility for each pushed commit?

I was assuming it happened as you run python2.4 so it is out of question.


Regards,
Jan

References:
- [python] Implement gdb.search_memory.
  - From: Thiago Jung Bauermann
- Re: [python] Implement gdb.search_memory.
  - From: Jan Kratochvil
- Re: [python] Implement gdb.search_memory.
  - From: Phil Muldoon
- Re: [python] Implement gdb.search_memory.
  - From: Thiago Jung Bauermann

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]