linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shriek <shriek.007@gmail.com>
To: Vadiraj <vadiraj.cs@gmail.com>, Mihai Dontu <mdontu@bitdefender.com>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: Where to find definition for __FUNCTION__ macro
Date: Wed, 23 Aug 2006 16:18:49 +0530	[thread overview]
Message-ID: <3ce33f6c0608230348s1cd6d5a1yf8b54d1eb830fffa@mail.gmail.com> (raw)
In-Reply-To: <6eee1c40608230324t63154c45xa4b54c6d6cc9850d@mail.gmail.com>

Alright, I might just as well present my problem here... I am trying
to debug some call back handlers which are actualy registered as
function pointers at boot time for a router, now lets say there is  a
central notification framework and looking at the msg-type it calls a
specific handler, so there is some statement like

               ev_msg_handlers[msg->rtsm_type].
So I was thinking if I could get the internals of the __FUNCTION__
macro and if my assumption that it looks it up in system map then I
could possibly attempt to modify it so as to accept the handler
address and return the function name it is entering ... what say ???

On 8/23/06, Vadiraj <vadiraj.cs@gmail.com> wrote:
> __FUNCTION__ is not defined macro part of compiler(GCC).
>
>
> On 8/23/06, Shriek <shriek.007@gmail.com> wrote:
> >
> Hi
>   Where can I find the implementation of the __FUNCTION__ macro, does
> it use symbol table look up  or something ... thanks and regards ...
>
> Shrikanth R K
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-c-programming" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at
> http://vger.kernel.org/majordomo-info.html
>
>
>
>
> --
> cheers,
> Vadi

  parent reply	other threads:[~2006-08-23 10:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-23 10:02 Where to find definition for __FUNCTION__ macro Shriek
2006-08-23 10:13 ` Mihai Dontu
     [not found] ` <6eee1c40608230324t63154c45xa4b54c6d6cc9850d@mail.gmail.com>
2006-08-23 10:48   ` Shriek [this message]
2006-08-23 11:11     ` Glynn Clements
2006-08-23 12:49       ` Shorty Porty

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=3ce33f6c0608230348s1cd6d5a1yf8b54d1eb830fffa@mail.gmail.com \
    --to=shriek.007@gmail.com \
    --cc=linux-c-programming@vger.kernel.org \
    --cc=mdontu@bitdefender.com \
    --cc=vadiraj.cs@gmail.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;
as well as URLs for NNTP newsgroup(s).