[Mono-aspnet-list] SIGSEGV error, no idea why?

Piercy michael_pierce at hotmail.co.uk
Fri Jul 17 05:02:20 EDT 2009


Ok had a quick whizz through the trace file and i cannot see any line
identation. Everythings indented the same apart from certain sections which
are xml.  Ill paste the two file below if you wish feel free to take a look.
Like i say i did have a look and cant see any indentation.  Ill try compile
mono from svn now :)

i have two log files.  one i did:
MONO_OPTIONS=--trace xsp2 --nonstop --port 8181 --applications
/home/user/public_html/weddingsite:. 

this generated a 160MB trace.log file which can be downloaded here:
www.1hess.com/cpwedding/trace.log

i then did:
MONO_OPTIONS=--trace xsp2 --nonstop --port 8181 N:WeddingSite
/usr/local/lib/mono/2.0/xsp2.exe >> fileOut.txt

and got a 44mb log file (which is similar)

and can be found at:
www.1hess.com/cpwedding/fileOut.txt


Thanks once again,
Piercy


> trace.log 2>&1

Marek Habersack-6 wrote:
> 
> Piercy wrote:
>> OK right just to make sure i did this right ill list exactly what i did:
>> 
>> 1) open shell
>> 
>> 2) cd /home/user/public_html/weddingsite
>> 
>> 3) MONO_OPTIONS=--trace xsp2 --nonstop --port 8181 --applications
>> /home/user/public_html/weddingsite:. > trace.log 2>&1
>> 
>> 4) wget http://localhost:8181
>> 
>> 5) tail -n100 trace.log
>> 
>> output: http://piercy.pastebin.com/da70995a
>> 
>> this file is 164mb big and it was only running about 30 seconds.  maybe i
>> will need to analyze the whole file?
> It would seem so, alas. Fortunately, it should be pretty easy - you need
> to look for increasing line 
>   indentation, which singals recursive calls, so you don't really need to
> read the log until you 
> find that pattern. The part you pasted deals with reading some XML input
> and looks pretty standard.
> If you have a chance, try running your app with Mono from svn trunk to see
> if it still breaks there 
> (here's a short HOWTO: http://mono-project.com/Compiling_Mono_From_SVN)
> 
> marek
>> 
>> 
>> Many thanks for your help,
>> 
>> Piercy
>> 
>> 
>> 
>> 
>> 
>> Robert Jordan wrote:
>>> Piercy wrote:
>>>> Ok, i tried my best to trace this.  I didnt do it on xsp (because i
>>>> have
>>>> no
>>>> idea how that works or anything so jsut used apache). i navigated to
>>>> the
>>>> ASP
>>>> .Net sites bin folder and did "mono --trace WeddingSite.dll >>
>>>> fileOut.txt"
>>>> (is this correct?).  The output i got was this:
>>> It's not correct. Try this:
>>>
>>> 1) open a shell
>>>
>>> 2) change into your app's directory
>>>
>>> 3) execute:
>>>
>>>     MONO_OPTIONS=--trace xsp2 --nonstop --port 8181 --applications /:. > 
>>> trace.log 2>&1
>>>
>>> 4) navigate to http://localhost:8181/ and try to trigger the crash
>>>
>>> 5) execute
>>>
>>>     tail -n100 trace.log
>>>
>>> 6) post the output of (5)
>>>
>>>
>>> If your application's virtual root isn't "/" then adjust
>>> the --applications switch accordingly:
>>>
>>> --applications /foo:.
>>>
>>> Robert
>>>
>>> _______________________________________________
>>> Mono-aspnet-list mailing list
>>> Mono-aspnet-list at lists.ximian.com
>>> http://lists.ximian.com/mailman/listinfo/mono-aspnet-list
>>>
>>>
>> 
> 
> _______________________________________________
> Mono-aspnet-list mailing list
> Mono-aspnet-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-aspnet-list
> 
> 

-- 
View this message in context: http://www.nabble.com/SIGSEGV-error%2C-no-idea-why--tp24512994p24530956.html
Sent from the Mono - ASP.NET mailing list archive at Nabble.com.



More information about the Mono-aspnet-list mailing list