From: Kevin Buettner <kevinb@cygnus.com>
To: Daniel Berlin <dberlin@redhat.com>
Cc: Elena Zannoni <ezannoni@redhat.com>,
Jim Wilson <wilson@cygnus.com>, Pete Wyckoff <pw@osc.edu>,
gdb@sources.redhat.com
Subject: Re: [Linux-ia64] Re: gdb null ptr
Date: Mon, 06 Nov 2000 17:08:00 -0000 [thread overview]
Message-ID: <1001107010812.ZM16938@ocotillo.lan> (raw)
In-Reply-To: <m3em0sqv74.fsf@dan2.cygnus.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 3743 bytes --]
[CC to linux-ia64@linuxia64.org trimmed since this is primarly a gdb
matter.]
On Nov 3, 10:20pm, Daniel Berlin wrote:
> > I will leave it to the dwarf2 maintainers to decide whether this
> > patch is acceptable or if it would be better to implement one of
> > Jim's other suggestions.
> >
>
> Unfortuantely , this is actually still wrong for languages other than
> C++, because we don't have the same guarantees about uniqueness in the name.
>
> I was actually in the process of readying patches that add the same
> type of name based caching (based on mangled name) to partial and
> normal symbol reading, which gives us an amazing win for C++.
>
> These patches also moved all of the name caching into "if (cu_language
> == language_cplus)" blocks, doing what we used to do in the old case
> (IE no caching).
>
> Rather than let this stay broken until i finish cleaning up those
> patches, here is a patch that moves the type caching so it only
> happens for C++ CU's.
I hereby withdraw my patch from consideration in favor of Daniel's
patch. In my opinion, Daniel's patch should go in ASAP since the code
in question has been broken since June 5 according to cvs annotate.
For some reason, the corresponding ChangeLog entry is May 30.
The other alternative is to revert the May 30/June 5 patch.
> Unless other languages make the same guarantees, we can't do the same
> optimization.
Agreed. I've constructed a small example and have convinced myself that
the code presently in dwarf2read.c is broken for C, but not for C++.
> I have added the same type of code kevin has to the patches i am
> readying.
Good.
You may wish to prepare a new interim patch which has a proper
ChangeLog entry, fixes the formatting of the long ``nameoftype = ...''
line, and which incorporates my proposed fix of not caching the type
unless it has a name or tag name. This latter check is still
necessary to account for error conditions in reading the type die. If
you feel that you do not have time to do this, let me know, and I'll
put it together for you.
Kevin
From inksupplies@kt.com.ar Mon Nov 06 18:39:00 2000
From: inksupplies <inksupplies@kt.com.ar>
To: gdb@sourceware.cygnus.com
Subject: Ahora imprima todo y gaste MENOS!!!
Date: Mon, 06 Nov 2000 18:39:00 -0000
Message-id: <e856f62b2cd17d16bf5908f8f627f5eb@NO-ID-FOUND.mhonarc.org>
X-SW-Source: 2000-11/msg00030.html
Content-length: 1348
Title: Si los cartuchos de su impresora a chorro de tinta
Si los cartuchos de su impresora a chorro de
tinta
Canon - Epson - Hewlett Packard - Lexmark
le resultan caros... CLIQUEE AQUI !!!
Informándonos la marca y modelo de su
impresora
comenzará a ahorrar más de un 50% en sus
costos de impresión
NOTA: Su dirección nos
fue proporcionada como interesada en recibir esta
información, en caso de no ser asÃ, rogamos disculpar la
intromisión y responder este mensaje - Cliqueando en el
siguiente link> Asunto: REMOVE [no recibirá nuevos mensajes]
Queremos comunicarnos con Ud.de la forma
más saludable posible.
" NO MALGASTEMOS TANTO PAPEL EN
PUBLICIDAD Y SE TALARAN MENOS ÃRBOLES"
!!! LA UTILIZACION DEL CORREO
ELECTRÃNICO PRESERVA EL MEDIO AMBIENTE !!!
Bajo
el Decreto S.1618 TITULO III aprobado por el 105 Congreso
base de las normativas internacionales sobre SPAM, esta carta
no puede ser considerada SPAM mientras incluya una forma de
ser removido y usted puede hacerlo ahora mismo respondiendo
este e-mail con "remover" en el asunto. Gracias, y
disculpe las molestias que pudiéramos haberle ocasionado en
caso de que ésta información no sea de su interés.
next prev parent reply other threads:[~2000-11-06 17:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200011032142.NAA27103@wilson.cygnus.com>
[not found] ` <1001103230254.ZM14396@ocotillo.lan>
2000-11-03 19:21 ` Daniel Berlin
2000-11-06 17:08 ` Kevin Buettner [this message]
2000-11-06 21:13 ` Daniel Berlin
[not found] <npofzr8lj2.fsf@zwingli.cygnus.com>
2000-11-07 15:40 ` Jim Wilson
2000-11-09 14:03 David B Anderson
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=1001107010812.ZM16938@ocotillo.lan \
--to=kevinb@cygnus.com \
--cc=dberlin@redhat.com \
--cc=ezannoni@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=pw@osc.edu \
--cc=wilson@cygnus.com \
/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