Prev: Loop thru WinForm Controls
Next: Multilingual application
From: Gilbert Tordeur on 26 Apr 2010 09:40
Hi Phill.

(back from holiday)

ildasm, this is the tool I was missing (because of my ignorance).

Many thanks for your answer, I was able to identify the wrong statement.

Have a good day,
Gilbert


"Phill W." <p-.-a-.-w-a-r-d-@-o-p-e-n-.-a-c-.-u-k> a �crit dans le message
de news: hq1vub$nfp$1(a)south.jnrs.ja.net...
> On 12/04/2010 10:14, Gilbert Tordeur wrote:
>
>> An ASP.NET application reports the following error :
>>
>> ...
>> [NullReferenceException: Object reference not set to an instance of an
>> object.]
>> RefFlu050.Page_Load(Object sender, EventArgs e) +1174
>
>> How can I identify which statement in my source code corresponds to
>> RefFlu050.Page_Load +1174 ?
>
> "+1174" denotes an offset into I.L. Code and not a line number.
>
> You know which routine the exception occurred in (RefFlu050.Page_Load), so
> you can use ildasm to "pull apart" that particular method. The offsets
> appear down the lefthand side, prefixed with "IL_":
>
> IL_001b: ldloc.1
> IL_001c: ldarg.1
> IL_001d: ldarg.2
> IL_001e: ldarg.3
> IL_001f: callvirt instance class [System.Data]System.Data.DataSet
> [A.B.C.Processor]A.B.C.ID::E(string,
> class [A.B.MiddleTier]A.B.C/ClientData,
> class [A.B.Errors]A.B.IC&)
> IL_0024: stind.ref
> IL_0025: ldarg.3
> IL_0026: ldind.ref
>
> The "callvirt" entries are probably the most important ones, being calls
> to others methods, hopefully ones that you wrote.
>
> HTH,
> Phill W.


First  |  Prev  | 
Pages: 1 2
Prev: Loop thru WinForm Controls
Next: Multilingual application