|
From: Ibrahim <be_...@ya...> - 2006-03-14 23:46:32
|
hi, i'm working under linux/RTAI platform and when exceuting my application, named "testPropagation" i had a segmentation fault error!! that's why i'm trying valgrind tool for debugging my application. the commande line i type: "valgrind -v ./testPropagation" and as it seems there was a problem when debugging: as it seems valgrind has killed my application because it doesn't recognise lxrt library!! this is the result of the command line above: ==5579== My PID = 5579, parent PID = 2848. Prog and args are: ==5579== ./testPropagation ==5579== --5579-- --5579-- Command line --5579-- ./testPropagation --5579-- Startup, with flags: --5579-- -v --5579-- --log-file=memcheckresukt --5579-- Contents of /proc/version: --5579-- Linux version 2.6.8.1-adeos (brahimos@localhost.localdomain) (version gcc 3.3.3 20040412 (Red Hat Linux 3.3.3-7)) #1 Mon Jan 10 01:42:11 CET 2005 --5579-- Arch and subarch: X86, x86-sse2 --5579-- Valgrind library directory: /usr/local/lib/valgrind --5579-- Reading syms from /lib/ld-2.3.3.so (0xB1A000) --5579-- Reading syms from /home/brahimos/manip/copie_test4/testPropagation (0x8048000) --5579-- Reading syms from /usr/local/lib/valgrind/x86-linux/memcheck (0xB0000000) --5579-- object doesn't have a dynamic symbol table --5579-- Reading suppressions file: /usr/local/lib/valgrind/default.supp --5579-- REDIR: 0xB2B400 (index) redirected to 0xB001AE72 (vgPlain_x86_linux_REDIR_FOR_index) --5579-- Reading syms from /usr/local/lib/valgrind/x86-linux/vgpreload_core.so (0x4000000) --5579-- Reading syms from /usr/local/lib/valgrind/x86-linux/vgpreload_memcheck.so (0x4003000) --5579-- REDIR: 0xB2B5A0 (strlen) redirected to 0x4005F8C (strlen) --5579-- Reading syms from /lib/tls/libpthread-0.61.so (0xD6C000) --5579-- Reading syms from /usr/lib/libstdc++.so.5.0.5 (0x6A16000) --5579-- object doesn't have a symbol table --5579-- Reading syms from /lib/tls/libm-2.3.3.so (0xC54000) --5579-- Reading syms from /lib/libgcc_s-3.3.3-20040413.so.1 (0xAD3000) --5579-- object doesn't have a symbol table --5579-- Reading syms from /lib/tls/libc-2.3.3.so (0xB37000) --5579-- REDIR: 0xB1A7A0 (_dl_sysinfo_int80) redirected to 0xB001AE6F (???) --5579-- REDIR: 0xB9E880 (memset) redirected to 0x4006680 (memset) --5579-- REDIR: 0xB9DAE0 (rindex) redirected to 0x4005C88 (rindex) --5579-- REDIR: 0xB9D250 (strcpy) redirected to 0x4005FC4 (strcpy) --5579-- REDIR: 0xB9ED50 (memcpy) redirected to 0x40062A4 (memcpy) --5579-- REDIR: 0xB9D820 (strnlen) redirected to 0x4005F4C (strnlen) --5579-- REDIR: 0xB97010 (malloc) redirected to 0x40043EE (malloc) --5579-- REDIR: 0xB9D770 (strlen) redirected to 0x4005F70 (strlen) --5579-- REDIR: 0x6AA9380 (operator new(unsigned)) redirected to 0x4004779 (operator new(unsigned)) --5579-- REDIR: 0xB9E820 (memmove) redirected to 0x40066A8 (memmove) vex x86->IR: unhandled instruction bytes: 0xCD 0xE3 0x89 0x3 ==5579== Your program just tried to execute an instruction that Valgrind ==5579== did not recognise. There are two possible reasons for this. ==5579== 1. Your program has a bug and erroneously jumped to a non-code ==5579== location. If you are running Memcheck and you just saw a ==5579== warning about a bad jump, it's probably your program's fault. ==5579== 2. The instruction is legitimate but Valgrind doesn't handle it, ==5579== i.e. it's Valgrind's fault. If you think this is the case or ==5579== you are not sure, please let us know. ==5579== Either way, Valgrind will now raise a SIGILL signal which will ==5579== probably kill your program. ==5579== ==5579== Process terminating with default action of signal 4 (SIGILL) ==5579== Illegal opcode at address 0x806B8BB ==5579== at 0x806B8BB: _rtai_lxrt (in /home/brahimos/manip/copie_test4/testPropagation) ==5579== by 0x806BB65: TPCommReceptor::TPCommReceptor() (in /home/brahimos/manip/copie_test4/testPropagation) ==5579== by 0x80688D6: TokenPlayer::TokenPlayer() (in /home/brahimos/manip/copie_test4/testPropagation) ==5579== by 0x8068B5F: TokenPlayer::tokenPlayerCreate() (in /home/brahimos/manip/copie_test4/testPropagation) ==5579== by 0x80642AE: main (in /home/brahimos/manip/copie_test4/testPropagation) --5579-- REDIR: 0xB996B0 (free) redirected to 0x4004EE5 (free) ==5579== ==5579== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 17 from 1) --5579-- --5579-- supp: 17 Ugly strchr error in /lib/ld-2.3.3.so ==5579== malloc/free: in use at exit: 14,084 bytes in 138 blocks. ==5579== malloc/free: 138 allocs, 0 frees, 14,084 bytes allocated. ==5579== ==5579== searching for pointers to 138 not-freed blocks. ==5579== checked 117,764 bytes. ==5579== ==5579== LEAK SUMMARY: ==5579== definitely lost: 20 bytes in 1 blocks. ==5579== possibly lost: 472 bytes in 14 blocks. ==5579== still reachable: 13,592 bytes in 123 blocks. ==5579== suppressed: 0 bytes in 0 blocks. ==5579== Use --leak-check=full to see details of leaked memory. --5579-- memcheck: sanity checks: 6 cheap, 1 expensive --5579-- memcheck: auxmaps: 0 auxmap entries (0k, 0M) in use --5579-- memcheck: auxmaps: 0 searches, 0 comparisons --5579-- memcheck: secondaries: 18 issued (1152k, 1M) --5579-- memcheck: secondaries: 29 accessible and distinguished (1856k, 1M) --5579-- tt/tc: 8,836 tt lookups requiring 9,121 probes --5579-- tt/tc: 8,836 fast-cache updates, 3 flushes --5579-- translate: new 4,299 (99,337 -> 1,740,262; ratio 175:10) [0 scs] --5579-- translate: dumped 0 (0 -> ??) --5579-- translate: discarded 8 (187 -> ??) --5579-- scheduler: 343,044 jumps (bb entries). --5579-- scheduler: 6/4,780 major/minor sched events. --5579-- sanity: 7 cheap, 1 expensive checks. --5579-- exectx: 30,011 lists, 146 contexts (avg 0 per list) --5579-- exectx: 155 searches, 9 full compares (58 per 1000) --5579-- exectx: 0 cmp2, 49 cmp4, 0 cmpAll thanks for any help, Ibrahim ___________________________________________________________________________ Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs exceptionnels pour appeler la France et l'international. Téléchargez sur http://fr.messenger.yahoo.com |
|
From: Alasdair F. <ala...@sp...> - 2006-03-15 08:01:18
|
Ibrahim, Your problem is an unhandled instruction, ie one that Valgrind doesn't understand: > vex x86->IR: unhandled instruction bytes: 0xCD 0xE3 0x89 0x3 No idea what it might be, as I'm purely a user! If you're not using 3.1.0 (ie the latest) try that, otherwise try the code direct from SVN. There are details on the website (www.valgrind.org) on how to obtain & compile both. Alasdair > i'm working under linux/RTAI platform and when > exceuting my application, named "testPropagation" i > had a segmentation fault error!! that's why i'm trying > valgrind tool for debugging my application. > the commande line i type: > > "valgrind -v ./testPropagation" > and as it seems there was a problem when debugging: as > it seems valgrind has killed my application because it > doesn't recognise lxrt library!! > > this is the result of the command line above: > > ==5579== My PID = 5579, parent PID = 2848. Prog and > args are: > ==5579== ./testPropagation > ==5579== > --5579-- > --5579-- Command line > --5579-- ./testPropagation > --5579-- Startup, with flags: > --5579-- -v > --5579-- --log-file=memcheckresukt > --5579-- Contents of /proc/version: > --5579-- Linux version 2.6.8.1-adeos > (brahimos@localhost.localdomain) (version gcc 3.3.3 > 20040412 (Red Hat Linux 3.3.3-7)) #1 Mon Jan 10 > 01:42:11 CET 2005 > --5579-- Arch and subarch: X86, x86-sse2 > --5579-- Valgrind library directory: > /usr/local/lib/valgrind > --5579-- Reading syms from /lib/ld-2.3.3.so (0xB1A000) > --5579-- Reading syms from > /home/brahimos/manip/copie_test4/testPropagation > (0x8048000) > --5579-- Reading syms from > /usr/local/lib/valgrind/x86-linux/memcheck > (0xB0000000) > --5579-- object doesn't have a dynamic symbol table > --5579-- Reading suppressions file: > /usr/local/lib/valgrind/default.supp > --5579-- REDIR: 0xB2B400 (index) redirected to > 0xB001AE72 (vgPlain_x86_linux_REDIR_FOR_index) > --5579-- Reading syms from > /usr/local/lib/valgrind/x86-linux/vgpreload_core.so > (0x4000000) > --5579-- Reading syms from > /usr/local/lib/valgrind/x86-linux/vgpreload_memcheck.so > (0x4003000) > --5579-- REDIR: 0xB2B5A0 (strlen) redirected to > 0x4005F8C (strlen) > --5579-- Reading syms from /lib/tls/libpthread-0.61.so > (0xD6C000) > --5579-- Reading syms from /usr/lib/libstdc++.so.5.0.5 > (0x6A16000) > --5579-- object doesn't have a symbol table > --5579-- Reading syms from /lib/tls/libm-2.3.3.so > (0xC54000) > --5579-- Reading syms from > /lib/libgcc_s-3.3.3-20040413.so.1 (0xAD3000) > --5579-- object doesn't have a symbol table > --5579-- Reading syms from /lib/tls/libc-2.3.3.so > (0xB37000) > --5579-- REDIR: 0xB1A7A0 (_dl_sysinfo_int80) > redirected to 0xB001AE6F (???) > --5579-- REDIR: 0xB9E880 (memset) redirected to > 0x4006680 (memset) > --5579-- REDIR: 0xB9DAE0 (rindex) redirected to > 0x4005C88 (rindex) > --5579-- REDIR: 0xB9D250 (strcpy) redirected to > 0x4005FC4 (strcpy) > --5579-- REDIR: 0xB9ED50 (memcpy) redirected to > 0x40062A4 (memcpy) > --5579-- REDIR: 0xB9D820 (strnlen) redirected to > 0x4005F4C (strnlen) > --5579-- REDIR: 0xB97010 (malloc) redirected to > 0x40043EE (malloc) > --5579-- REDIR: 0xB9D770 (strlen) redirected to > 0x4005F70 (strlen) > --5579-- REDIR: 0x6AA9380 (operator new(unsigned)) > redirected to 0x4004779 (operator new(unsigned)) > --5579-- REDIR: 0xB9E820 (memmove) redirected to > 0x40066A8 (memmove) > vex x86->IR: unhandled instruction bytes: 0xCD 0xE3 > 0x89 0x3 > ==5579== Your program just tried to execute an > instruction that Valgrind > ==5579== did not recognise. There are two possible > reasons for this. > ==5579== 1. Your program has a bug and erroneously > jumped to a non-code > ==5579== location. If you are running Memcheck and > you just saw a > ==5579== warning about a bad jump, it's probably > your program's fault. > ==5579== 2. The instruction is legitimate but Valgrind > doesn't handle it, > ==5579== i.e. it's Valgrind's fault. If you think > this is the case or > ==5579== you are not sure, please let us know. > ==5579== Either way, Valgrind will now raise a SIGILL > signal which will > ==5579== probably kill your program. > ==5579== > ==5579== Process terminating with default action of > signal 4 (SIGILL) > ==5579== Illegal opcode at address 0x806B8BB > ==5579== at 0x806B8BB: _rtai_lxrt (in > /home/brahimos/manip/copie_test4/testPropagation) > ==5579== by 0x806BB65: > TPCommReceptor::TPCommReceptor() (in > /home/brahimos/manip/copie_test4/testPropagation) > ==5579== by 0x80688D6: TokenPlayer::TokenPlayer() > (in /home/brahimos/manip/copie_test4/testPropagation) > ==5579== by 0x8068B5F: > TokenPlayer::tokenPlayerCreate() (in > /home/brahimos/manip/copie_test4/testPropagation) > ==5579== by 0x80642AE: main (in > /home/brahimos/manip/copie_test4/testPropagation) > --5579-- REDIR: 0xB996B0 (free) redirected to > 0x4004EE5 (free) > ==5579== > ==5579== ERROR SUMMARY: 0 errors from 0 contexts > (suppressed: 17 from 1) > --5579-- > --5579-- supp: 17 Ugly strchr error in > /lib/ld-2.3.3.so > ==5579== malloc/free: in use at exit: 14,084 bytes in > 138 blocks. > ==5579== malloc/free: 138 allocs, 0 frees, 14,084 > bytes allocated. > ==5579== > ==5579== searching for pointers to 138 not-freed > blocks. > ==5579== checked 117,764 bytes. > ==5579== > ==5579== LEAK SUMMARY: > ==5579== definitely lost: 20 bytes in 1 blocks. > ==5579== possibly lost: 472 bytes in 14 blocks. > ==5579== still reachable: 13,592 bytes in 123 > blocks. > ==5579== suppressed: 0 bytes in 0 blocks. > ==5579== Use --leak-check=full to see details of > leaked memory. > --5579-- memcheck: sanity checks: 6 cheap, 1 > expensive > --5579-- memcheck: auxmaps: 0 auxmap entries (0k, 0M) > in use > --5579-- memcheck: auxmaps: 0 searches, 0 comparisons > --5579-- memcheck: secondaries: 18 issued (1152k, 1M) > --5579-- memcheck: secondaries: 29 accessible and > distinguished (1856k, 1M) > --5579-- tt/tc: 8,836 tt lookups requiring 9,121 > probes > --5579-- tt/tc: 8,836 fast-cache updates, 3 > flushes > --5579-- translate: new 4,299 (99,337 -> > 1,740,262; ratio 175:10) [0 scs] > --5579-- translate: dumped 0 (0 -> ??) > --5579-- translate: discarded 8 (187 -> ??) > --5579-- scheduler: 343,044 jumps (bb entries). > --5579-- scheduler: 6/4,780 major/minor sched events. > --5579-- sanity: 7 cheap, 1 expensive checks. > --5579-- exectx: 30,011 lists, 146 contexts (avg 0 > per list) > --5579-- exectx: 155 searches, 9 full compares (58 > per 1000) > --5579-- exectx: 0 cmp2, 49 cmp4, 0 cmpAll > -- ------------------------------------------------------------------------ Alasdair Ferro SpiraTech Ltd, Product Engineer Carrington Business Park, mailto:ala...@sp... Manchester, Work: +44 (0)161 776 4582 M31 4DD, U.K. http://www.spiratech.com ------------------------------------------------------------------------ This email and any files transmitted with it are confidential and may be legally privileged. It is intended solely for the use of the individual or entity to whom it is addressed. If you have received this in error, please contact the sender and delete the material immediately. Whilst this email has been swept for viruses, you should carry out your own virus check before opening any attachment. SpiraTech Ltd accepts no liability for any loss or damage which may be caused by software viruses or interception or interruption of this email. |
|
From: Ibrahim <be_...@ya...> - 2006-03-15 14:01:50
|
> Your problem is an unhandled instruction, ie one > that Valgrind doesn't > understand: > > > vex x86->IR: unhandled instruction bytes: 0xCD > 0xE3 0x89 0x3 > > No idea what it might be, as I'm purely a user! If > you're not using > 3.1.0 (ie the latest) try that, otherwise try the > code direct from SVN. > There are details on the website (www.valgrind.org) > on how to obtain & > compile both. > > Alasdair i'm using the 3.1.0 version of valgrind (Linux 2.6.8 and RTAI 3.1). what did u mean by SVN??? thanks > > i'm working under linux/RTAI platform and when > > exceuting my application, named "testPropagation" > i > > had a segmentation fault error!! that's why i'm > trying > > valgrind tool for debugging my application. > > the commande line i type: > > > > "valgrind -v ./testPropagation" > > and as it seems there was a problem when > debugging: as > > it seems valgrind has killed my application > because it > > doesn't recognise lxrt library!! > > > > this is the result of the command line above: > > > > ==5579== My PID = 5579, parent PID = 2848. Prog > and > > args are: > > ==5579== ./testPropagation > > ==5579== > > --5579-- > > --5579-- Command line > > --5579-- ./testPropagation > > --5579-- Startup, with flags: > > --5579-- -v > > --5579-- --log-file=memcheckresukt > > --5579-- Contents of /proc/version: > > --5579-- Linux version 2.6.8.1-adeos > > (brahimos@localhost.localdomain) (version gcc > 3.3.3 > > 20040412 (Red Hat Linux 3.3.3-7)) #1 Mon Jan 10 > > 01:42:11 CET 2005 > > --5579-- Arch and subarch: X86, x86-sse2 > > --5579-- Valgrind library directory: > > /usr/local/lib/valgrind > > --5579-- Reading syms from /lib/ld-2.3.3.so > (0xB1A000) > > --5579-- Reading syms from > > /home/brahimos/manip/copie_test4/testPropagation > > (0x8048000) > > --5579-- Reading syms from > > /usr/local/lib/valgrind/x86-linux/memcheck > > (0xB0000000) > > --5579-- object doesn't have a dynamic symbol > table > > --5579-- Reading suppressions file: > > /usr/local/lib/valgrind/default.supp > > --5579-- REDIR: 0xB2B400 (index) redirected to > > 0xB001AE72 (vgPlain_x86_linux_REDIR_FOR_index) > > --5579-- Reading syms from > > > /usr/local/lib/valgrind/x86-linux/vgpreload_core.so > > (0x4000000) > > --5579-- Reading syms from > > > /usr/local/lib/valgrind/x86-linux/vgpreload_memcheck.so > > (0x4003000) > > --5579-- REDIR: 0xB2B5A0 (strlen) redirected to > > 0x4005F8C (strlen) > > --5579-- Reading syms from > /lib/tls/libpthread-0.61.so > > (0xD6C000) > > --5579-- Reading syms from > /usr/lib/libstdc++.so.5.0.5 > > (0x6A16000) > > --5579-- object doesn't have a symbol table > > --5579-- Reading syms from /lib/tls/libm-2.3.3.so > > (0xC54000) > > --5579-- Reading syms from > > /lib/libgcc_s-3.3.3-20040413.so.1 (0xAD3000) > > --5579-- object doesn't have a symbol table > > --5579-- Reading syms from /lib/tls/libc-2.3.3.so > > (0xB37000) > > --5579-- REDIR: 0xB1A7A0 (_dl_sysinfo_int80) > > redirected to 0xB001AE6F (???) > > --5579-- REDIR: 0xB9E880 (memset) redirected to > > 0x4006680 (memset) > > --5579-- REDIR: 0xB9DAE0 (rindex) redirected to > > 0x4005C88 (rindex) > > --5579-- REDIR: 0xB9D250 (strcpy) redirected to > > 0x4005FC4 (strcpy) > > --5579-- REDIR: 0xB9ED50 (memcpy) redirected to > > 0x40062A4 (memcpy) > > --5579-- REDIR: 0xB9D820 (strnlen) redirected to > > 0x4005F4C (strnlen) > > --5579-- REDIR: 0xB97010 (malloc) redirected to > > 0x40043EE (malloc) > > --5579-- REDIR: 0xB9D770 (strlen) redirected to > > 0x4005F70 (strlen) > > --5579-- REDIR: 0x6AA9380 (operator new(unsigned)) > > redirected to 0x4004779 (operator new(unsigned)) > > --5579-- REDIR: 0xB9E820 (memmove) redirected to > > 0x40066A8 (memmove) > > vex x86->IR: unhandled instruction bytes: 0xCD > 0xE3 > > 0x89 0x3 > > ==5579== Your program just tried to execute an > > instruction that Valgrind > > ==5579== did not recognise. There are two > possible > > reasons for this. > > ==5579== 1. Your program has a bug and erroneously > > jumped to a non-code > > ==5579== location. If you are running Memcheck > and > > you just saw a > > ==5579== warning about a bad jump, it's > probably > > your program's fault. > > ==5579== 2. The instruction is legitimate but > Valgrind > > doesn't handle it, > > ==5579== i.e. it's Valgrind's fault. If you > think > > this is the case or > > ==5579== you are not sure, please let us know. > > ==5579== Either way, Valgrind will now raise a > SIGILL > > signal which will > > ==5579== probably kill your program. > > ==5579== > > ==5579== Process terminating with default action > of > > signal 4 (SIGILL) > > ==5579== Illegal opcode at address 0x806B8BB > > ==5579== at 0x806B8BB: _rtai_lxrt (in > > /home/brahimos/manip/copie_test4/testPropagation) > > ==5579== by 0x806BB65: > > TPCommReceptor::TPCommReceptor() (in > > /home/brahimos/manip/copie_test4/testPropagation) > > ==5579== by 0x80688D6: > TokenPlayer::TokenPlayer() > > (in > /home/brahimos/manip/copie_test4/testPropagation) > > ==5579== by 0x8068B5F: > > TokenPlayer::tokenPlayerCreate() (in > > /home/brahimos/manip/copie_test4/testPropagation) > > ==5579== by 0x80642AE: main (in > > /home/brahimos/manip/copie_test4/testPropagation) > > --5579-- REDIR: 0xB996B0 (free) redirected to > > 0x4004EE5 (free) > > ==5579== > > ==5579== ERROR SUMMARY: 0 errors from 0 contexts > > (suppressed: 17 from 1) > > --5579-- > > --5579-- supp: 17 Ugly strchr error in > > /lib/ld-2.3.3.so > > ==5579== malloc/free: in use at exit: 14,084 bytes > in > > 138 blocks. > > ==5579== malloc/free: 138 allocs, 0 frees, 14,084 > > bytes allocated. > > ==5579== > > ==5579== searching for pointers to 138 not-freed > > blocks. > > ==5579== checked 117,764 bytes. > > ==5579== > > ==5579== LEAK SUMMARY: > > ==5579== definitely lost: 20 bytes in 1 blocks. > > ==5579== possibly lost: 472 bytes in 14 > blocks. > > ==5579== still reachable: 13,592 bytes in 123 > > blocks. > > ==5579== suppressed: 0 bytes in 0 blocks. > > ==5579== Use --leak-check=full to see details of > > leaked memory. > > --5579-- memcheck: sanity checks: 6 cheap, 1 > > expensive > > --5579-- memcheck: auxmaps: 0 auxmap entries (0k, > 0M) > > in use > > --5579-- memcheck: auxmaps: 0 searches, 0 > comparisons > > --5579-- memcheck: secondaries: 18 issued (1152k, > 1M) > > --5579-- memcheck: secondaries: 29 accessible and > > distinguished (1856k, 1M) > > --5579-- tt/tc: 8,836 tt lookups requiring > 9,121 > > probes > > --5579-- tt/tc: 8,836 fast-cache updates, 3 > === message truncated === ___________________________________________________________________________ Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs exceptionnels pour appeler la France et l'international. Téléchargez sur http://fr.messenger.yahoo.com |
|
From: Julian S. <js...@ac...> - 2006-03-15 10:54:30
|
> vex x86->IR: unhandled instruction bytes: 0xCD 0xE3 > 0x89 0x3 That's "int $0xE3", which is a pretty strange insn. Are you doing some strange hardware-related thing? Or perhaps it's to do with your RTAI distribution? J |
|
From: Ibrahim <be_...@ya...> - 2006-03-15 14:06:24
|
--- Julian Seward <js...@ac...> a écrit : > > > vex x86->IR: unhandled instruction bytes: 0xCD > 0xE3 > > 0x89 0x3 > > That's "int $0xE3", which is a pretty strange insn. > Are you how can i interpret this Hexadecimal information!! > doing some strange hardware-related thing? no i don't touch any hardware-related thing! >Or > perhaps it's to > do with your RTAI distribution? it's an RTAI3.1 under Linux2.6.8 did u confirm that it valgrind can debug an RTAI/LXRT process? best regards, > This SF.Net email is sponsored by xPML, a > groundbreaking scripting language > that extends applications into web and mobile media. > Attend the live webcast > and join the prime developer group breaking into > this new coding territory! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users > ___________________________________________________________________________ Nouveau : téléphonez moins cher avec Yahoo! Messenger. Appelez le monde entier à partir de 0,012 /minute ! Téléchargez sur http://fr.messenger.yahoo.com |
|
From: Dennis L. <pla...@in...> - 2006-03-15 16:50:33
|
Am Mittwoch, den 15.03.2006, 15:06 +0100 schrieb Ibrahim: > it's an RTAI3.1 under Linux2.6.8 > did u confirm that it valgrind can debug an RTAI/LXRT > process? > btw. ancient kernel... nevertheless, what exactly is rtai? I found rtai.org website, but cannot look at it, as it insists on using https with an invalid certificate. Did you check the source code, if it actual does use that kind of instructions? Do you need some special kernel patches or kernel modules for operating the system? greets Dennis |
|
From: Bryan M. <om...@br...> - 2006-03-15 21:05:16
|
RTAI is the non-patented realtime extension for linux (as opposed to the other one). It works by intercepting interrupts before the kernel gets them + some other stuff so you can have realtime response and scheduling but still have all the features of linux around in a non-realtime domain for doing logging or whatever. You have realtime fifos to squirt data between the domains + loads of other things as its been a while since I sized this up for a clients' project I was working on. Bryan Dennis Lubert wrote: > Am Mittwoch, den 15.03.2006, 15:06 +0100 schrieb Ibrahim: > >> it's an RTAI3.1 under Linux2.6.8 >> did u confirm that it valgrind can debug an RTAI/LXRT >> process? >> > btw. ancient kernel... > nevertheless, what exactly is rtai? I found rtai.org website, but cannot > look at it, as it insists on using https with an invalid certificate. > Did you check the source code, if it actual does use that kind of > instructions? Do you need some special kernel patches or kernel modules > for operating the system? > > greets > > Dennis > > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting language > that extends applications into web and mobile media. Attend the live webcast > and join the prime developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users > |