How can i read the stack frames of running process?

[CBFalconer]

.... snip ...


I disagree. From what I can see the "_ _" problem *is* a case of
incorrect spelling (but a well-intentioned one). It seems to have
been put in deliberately to make the double underscore obvious.
The "fi" ligature is simply correct and good quality PDF readers
will cut and paste it as "fi" (two characters) and match it in a
search for "f" followed by "i". In other words, it works just
fine.

I don't think either says anything about the penalty of PDF
publication. In fact for interactive (i.e. non scripted) searches
I like the PDF better, now. I can search for text, jump to
specific pages or go right to a given section just by typing any
part of the section number or name.

We'll just have to agree to disagree. My main point was that with
text you have no problem selecting the search software to suit your
tastes and needs.

 

[Mark McIntyre]

On Tue, 23 Oct 2007 06:14:22 GMT, in comp.lang.c ,

Or you could - perhaps? revolutionary idea, I know - check the index.

Typically, an index doesn't index every single word!

A - see pages 2-1200 inclusive.
But - see pages 2,3,4,5,6,7,8,11,12,14,16,....
for - see pages 2-1200 except 1104 and 896

--
Mark McIntyre

"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it."
--Brian Kernighan

 

[Richard Bos]

On Tue, 23 Oct 2007 06:14:22 GMT, in comp.lang.c ,


Typically, an index doesn't index every single word!

A - see pages 2-1200 inclusive.
But - see pages 2,3,4,5,6,7,8,11,12,14,16,....
for - see pages 2-1200 except 1104 and 896

Typically, one doesn't search for indefinite articles or coordinating
conjunctions. One searches for important nouns - precisely the ones that
are found in a good index. In this case, __func__ is in the index, while
__FUNCTION__ is not; one look at this index at the start of this whole
useless argument about PDF versus text versus underscores versus
identifiers would have settled the matter.

Richard

 

[Mark McIntyre]

On Fri, 26 Oct 2007 06:26:20 GMT, in comp.lang.c ,

In this case, __func__ is in the index, while
__FUNCTION__ is not; one look at this index at the start of this whole
useless argument about PDF versus text versus underscores versus
identifiers would have settled the matter.

I agree, but I think the point being made is that indices do not index
everything, and can thus only tell what _is_ in the book.
--
Mark McIntyre

"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it."
--Brian Kernighan

 

[Richard Bos]

I agree, but I think the point being made is that indices do not index
everything, and can thus only tell what _is_ in the book.

A good index, which I think one should assume the Standard does have,
indexes everything important. Thus, if something is not in the
Standard's index, either it isn't in the Standard, or it's only
mentioned in passing. Since __func__ is in it but __FUNCTION__ is not...
draw your own conclusion.

Richard

 

[Mark McIntyre]

I agree, but I think the point being made is that indices do not index
everything, and can thus only tell what _is_ in the book.

A good index, ....
indexes everything important. ....
Since __func__ is in it but __FUNCTION__ is not...
draw your own conclusion.[/QUOTE]

I agree, but its not a proof and cannot settle the matter.
--
Mark McIntyre

"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it."
--Brian Kernighan