Back to Home / #uml / 2013 / 10 / Prev Day | Next Day
#uml IRC Logs for 2013-10-08

---Logopened Tue Oct 08 00:00:53 2013
00:51-!-t4nk135 [~5329771e@webuser.thegrebs.com] has joined #uml
00:51<t4nk135:#uml>hi
00:53-!-t4nk135 [~5329771e@webuser.thegrebs.com] has quit []
08:52-!-Netsplit resistance.oftc.net <-> oxygen.oftc.net quits: hfb
08:56-!-hfb [~hfb@cpe-98-151-249-95.socal.res.rr.com] has joined #uml
10:29-!-hfb [~hfb@cpe-98-151-249-95.socal.res.rr.com] has quit [Quit: Leaving]
11:02-!-hfb [~hfb@pool-98-112-209-228.lsanca.dsl-w.verizon.net] has joined #uml
13:09-!-sysplex [~chatzilla@dslb-088-068-102-117.pools.arcor-ip.net] has joined #uml
13:09<sysplex:#uml>hi
13:10<sysplex:#uml>I try to run UML under gdb, but I receive SEGFAULTS.
13:10<sysplex:#uml>running the program on the commandline works fine, continue after the segfault, also seems to do the right thing. any ideas?
13:17<sysplex:#uml>e.g.: Program received signal SIGSEGV, Segmentation fault.
13:17<sysplex:#uml>0x00000000601cd65c in n_tty_open (tty=0x8ff21800) at drivers/tty/n_tty.c:1872
13:17<sysplex:#uml>1872 ldata->overrun_time = jiffies;
13:18<sysplex:#uml>(gdb) print ldata->overrun_time
13:18<sysplex:#uml>Cannot access memory at address 0x90876040
13:24<eegiks:#uml>ask gdb to ignore the segfaults, they are normal
13:52<sysplex:#uml>why doesn't gdb know about these memory regions?
14:14-!-sysplex [~chatzilla@dslb-088-068-102-117.pools.arcor-ip.net] has quit [Ping timeout: 480 seconds]
19:29-!-hfb [~hfb@pool-98-112-209-228.lsanca.dsl-w.verizon.net] has quit [Quit: Leaving]
22:52-!-hfb [~hfb@cpe-98-151-249-95.socal.res.rr.com] has joined #uml
23:59-!-VS_ChanLog [~stats@ns.theshore.net] has left #uml [Rotating Logs]
23:59-!-VS_ChanLog [~stats@ns.theshore.net] has joined #uml
---Logclosed Wed Oct 09 00:00:54 2013