[Mono-dev] Process background problem

[Carlos Ruiz Diaz]

My problem was solved but I want to publish its output of death

*This happens when I hit  ^C.*

Stacktrace:

  at (wrapper managed-to-native) System.Data.Odbc.libodbc.SQLFreeHandle
(uint16,intptr) <0x00004>
  at (wrapper managed-to-native) System.Data.Odbc.libodbc.SQLFreeHandle
(uint16,intptr) <0xffffffff>
  at System.Data.Odbc.OdbcCommand.FreeStatement () <0x00060>
  at System.Data.Odbc.OdbcCommand.Dispose (bool) <0x00014>
  at System.ComponentModel.Component.Finalize () <0x00010>
  at (wrapper runtime-invoke) System.Object.runtime_invoke_void__this__
(object,intptr,intptr,intptr) <0xffffffff>

Native stacktrace:

        mono [0x806cb79]
        mono [0x8084eb1]
        [0xb7f11440]
        /usr/lib/libodbc.so(SQLFreeHandle+0x25) [0xb6e4bb45]
        [0xb6359cd8]
        [0xb6359bc9]
        [0xb635a72d]
        [0xb635a6f9]
        [0xb7290f49]
        mono [0x81c2769]
        mono [0x816fc78]
        mono [0x81c2959]
        mono [0x81214b0]
        mono [0x814f9e5]
        mono [0x8168565]
        /lib/libpthread.so.0 [0xb7e38112]
        /lib/libc.so.6(clone+0x5e) [0xb7d9e2ee]

Debug info from gdb:

Quitting: ptrace: No existe el proceso.

*Or sometimes*

Thread 3 (Thread -1234777200 (LWP 19661)):
#0  0xb7f5f410 in ?? ()
#1  0xb666c1b4 in ?? ()
#2  0x00007497 in ?? ()
#3  0x00000000 in ?? ()

Thread 2 (Thread -1237382256 (LWP 19662)):
#0  0xb7f5f410 in ?? ()
#1  0xb63f01b4 in ?? ()
#2  0x00007499 in ?? ()
#3  0x00000000 in ?? ()

Thread 1 (Thread -1210922272 (LWP 18439)):
#0  0xb7f5f410 in ?? ()
#1  0xbfdaa480 in ?? ()
#2  0x08275ff4 in ?? ()
#3  0xbfdaa464 in ?? ()
#4  0xb7e8d876 in __nanosleep_nocancel () from /lib/libpthread.so.0
#5  0x0814e568 in SleepEx (ms=0, alertable=1) at threads.c:1018
#6  0x08120976 in ves_icall_System_Threading_Thread_Sleep_internal (ms=1000)
    at threads.c:1052
#7  0xb70ebd76 in ?? ()
#8  0x000003e8 in ?? ()
#9  0x08298298 in ?? ()
#10 0xb70ebc70 in ?? ()
#11 0x00065a80 in ?? ()
#12 0x00000001 in ?? ()
#13 0x0004e790 in ?? ()
#14 0x000003e8 in ?? ()
#15 0x00000003 in ?? ()
#16 0xbfdaa4d0 in ?? ()
#17 0xb70ebd54 in ?? ()
#18 0xbfdaa4e0 in ?? ()
#19 0xb70ebc86 in ?? ()
#20 0x000003e8 in ?? ()
#21 0x00042070 in ?? ()
#22 0xbfdaa534 in ?? ()
#23 0xb7a6986a in ?? ()
#24 0x000003e8 in ?? ()
#25 0x00065a80 in ?? ()
#26 0x00000002 in ?? ()
#27 0x00000000 in ?? ()
#0  0xb7f5f410 in ?? ()

=================================================================
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================


On Fri, Jan 16, 2009 at 3:08 PM, Carlos Ruiz Diaz <carlos.ruizdiaz at gmail.com
> wrote:

> You're right!!! it was a Console.Read() in my code that waits for a user
> input  in my very entry point at MainClass.Main(), it was a silly mistake.
>
> Thank you very  much for your help, it was really useful.
>
> CarlosRD
>
>
> On Fri, Jan 16, 2009 at 2:35 PM, Avery Pennarun <apenwarr at gmail.com>wrote:
>
>> 2009/1/16 Carlos Ruiz Diaz <carlos.ruizdiaz at gmail.com>:
>> > When I run the following command:
>> >
>> > mono program.exe
>> >
>> > everything behave as expected but running:
>> >
>> > mono program.exe&
>> >
>> > the program goes to background but almost immediately stops  so I use fg
>> > command to foreground the process and them seems to resume its execution
>> but
>> > sometimes when I do this and try to finish it using ^C (or SIGTERM) it
>> dies
>> > displaying a long stack trace apparently originated from a non-managed
>> code.
>>
>> Something in your program must be trying to read from stdin.  Can you
>> produce a minimal test case that will reproduce the problem?
>>
>> Avery
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/mono-devel-list/attachments/20090116/144d56ad/attachment.html