search for: setlin

Thanks for the help. I thought I'd solved the problem (setting the line number information in the instruction metadata) by inserting my own function for setting line number in llvm/Support/DebugLoc.h. I have added a function setLine(unsigned) in DebugLoc class. The function simply sets the LineCol variable as needed. But there is a problem. Whenever I'm checking the line number(calling getLine()) from the function where I've called setLine(...) function, it returns the changed line number but whenever I call the getL...

Hello all, OS name: FreeNAS 9.3 NUT version: 2.7.2 NUT installed method: Bundled with FreenNAS 9.3 Device: EATON 5SC 1000 (http://powerquality.eaton.com/Products-services/Backup-Power-UPS/5SC.aspx?cx=5&wtredirect=www.eaton.com/5SC&GUID=B81251A4-F34E-4373-94B3-B4FB3D0CBCA8) Problem description: This was originally reported as bug to FreeNAS

...vior (click to focus)? For example, if you change the mditest.rb example like so... --- mditest.rb 2007-04-18 16:19:59.000000000 -0700 +++ mdi.rb 2007-04-27 14:44:54.000000000 -0700 @@ -134,7 +134,7 @@ scrollwindow = FXScrollWindow.new(mdichild, 0) scrollwindow.verticalScrollBar.setLine(@font.fontHeight) btn = FXButton.new(scrollwindow, TYGER, - :opts => LAYOUT_FIX_WIDTH|LAYOUT_FIX_HEIGHT, :width => 600, :height => 1000) + :opts => LAYOUT_FIX_WIDTH|LAYOUT_FIX_HEIGHT, :width => 100, :height => 100) btn.font = @font btn.backColor = FX...

...cable, and report back > if everything is ok? > as a side note, debug timestamping is now available: ie: mge-shut -DDDT -a ... Network UPS Tools - MGE UPS SYSTEMS/SHUT driver 0.68 (2.4.1-1840:1845M) 14:27:25: debug level is '3' 14:27:25: entering upsdrv_initups() 14:27:25: entering setline(1) 14:27:25: entering shut_ups_start() ... This is effective for upsd, upsmon, upsdrvctl and the drivers by using "-T". The best, as told in the manpages, is to use it in conjunction with the debug flags (ie -D...) This should help out in troubleshooting timeframe problems. cheers, Arn...

...ow do I create MDNode* consisting of desired source line number. Source > line number can be extracted from the instruction-debug-info using > getMetadata method and then using getLineNumber method from DILocation > class. Unfortunately DILocation class does not have any function like > setLinenumber. You may want to check out Instruction::setDebugLoc(). llvm/Support/DebugLoc.h and llvm/Analysis/DIBuilder.h will likely be helpful as well.

...ng: --- ../nut-2.7.1/drivers/libshut.c 2013-10-02 14:16:42.000000000 +0200 +++ drivers/libshut.c 2014-02-25 16:39:34.000000000 +0100 @@ -312,7 +312,7 @@ /* FIXME: add variable baudrate detection */ *upsfd = ser_open(device_path); ser_set_speed(*upsfd, device_path, B2400); - setline(*upsfd, 0); + setline(*upsfd, 1); /* initialise communication */ if (!shut_synchronise(*upsfd)) This is tied to the PnP feature, and was reverted with the following commit: https://github.com/networkupstools/nut/commit/75b0ce8b952d7c55880f7a019ba61ec05b45e6a7 Never had time to get...

...Ghosh <abhirupju at gmail.com> wrote: > Thanks for the help. > I thought I'd solved the problem (setting the line number information in > the instruction metadata) by inserting my own function for setting line > number in llvm/Support/DebugLoc.h. I have added a function > setLine(unsigned) in DebugLoc class. The function simply sets the LineCol > variable as needed. But there is a problem. > > Whenever I'm checking the line number(calling getLine()) from the function > where I've called setLine(...) function, it returns the changed line number > but...

...is to be used. But how do I create MDNode* consisting of desired source line number. Source line number can be extracted from the instruction-debug-info using getMetadata method and then using getLineNumber method from DILocation class. Unfortunately DILocation class does not have any function like setLinenumber. Abhirup Ghosh M. Tech Department of Computer Science & Engg. IIT, Bombay email - abhirupju at gmail.com , abhirup at cse.iitb.ac.in Contact - 9920735181 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachm...

Good day to all, Gert Hulselmans requested a feature for MDISKCHK.COM that would function roughly like GETARGS.COM[1] by Murali Krishnan Ganapathy: DOS SET command output for MEMDISK kernel arguments passed by previous boot-loaders. He also needed to support the case for MEMDISK-in-a-MEMDISK type situations, where all MEMDISK kernel arguments could be gathered together and output as a list

...#39;s a good or a bad thing. Nevertheless I can't get it to react in any other way. This is what I get in both configurations: # /lib/nut/mge-shut -a mge-shut -D -D -D -D Network UPS Tools - MGE UPS SYSTEMS/SHUT driver 0.66 (2.2.2) debug level is '4' entering upsdrv_initups() entering setline(1) entering shut_ups_start() sent: (1 bytes) => 16 Syncing and notification setting done Communication with UPS established entering shut_get_descriptor(n 21, 9) entering shut_packet_send (8) shut_checksum = af sent: (11 bytes) => 81 88 81 06 00 21 00 00 09 00 af shut_wait_ack(): Nothing r...

...gt; > > > thanks for the confirmation with oldmge-shut. I'm not astonished on > the results, but was worth a try. > > I've double checked the related code difference for mge-shut between > 2.7.1 and 2.7.2. > Again, the only diff I see is the one pointed previously (setline...). > So, it would be great if you could test this patch (through some > reboots) and report back. > > Then, I don't think it's an issue with the device. > There is a long run TODO (mentioned in the header of libshut.c) that > is the baudrate negotiation. > The driv...

...libshut.c 2013-10-02 14:16:42.000000000 +0200 > +++ drivers/libshut.c 2014-02-25 16:39:34.000000000 +0100 > @@ -312,7 +312,7 @@ > /* FIXME: add variable baudrate detection */ > *upsfd = ser_open(device_path); > ser_set_speed(*upsfd, device_path, B2400); > - setline(*upsfd, 0); > + setline(*upsfd, 1); > > /* initialise communication */ > if (!shut_synchronise(*upsfd)) > > > This is tied to the PnP feature, and was reverted with the following > commit: > https://github.com/networkupstools/nut/commit/75b0ce8b952d7c55880f...

Hello Arno, > Question: have you also tested oldmge-shut? > Otherwise, that might be interesting to do so and send back the > results of these tests... Yes, I've tried this as well with worse results unfortunately. This driver seems to be even more unstable. When it gets able to set communication with the UPS (which is not always the case), it usually lost it again after a while.

...rial port of the machine and the UPS? > thanks for the confirmation with oldmge-shut. I'm not astonished on the results, but was worth a try. I've double checked the related code difference for mge-shut between 2.7.1 and 2.7.2. Again, the only diff I see is the one pointed previously (setline...). So, it would be great if you could test this patch (through some reboots) and report back. Then, I don't think it's an issue with the device. There is a long run TODO (mentioned in the header of libshut.c) that is the baudrate negotiation. The driver still communicates at 2400bauds,...

...t; > > > thanks for the confirmation with oldmge-shut. I'm not astonished on the > results, but was worth a try. > > I've double checked the related code difference for mge-shut between > 2.7.1 and 2.7.2. > Again, the only diff I see is the one pointed previously (setline...). > So, it would be great if you could test this patch (through some > reboots) and report back. > > Then, I don't think it's an issue with the device. > There is a long run TODO (mentioned in the header of libshut.c) that is > the baudrate negotiation. > The dr...

...with oldmge-shut. I'm not astonished >> on the results, but was worth a try. >> >> I've double checked the related code difference for mge-shut >> between 2.7.1 and 2.7.2. >> Again, the only diff I see is the one pointed previously >> (setline...). >> So, it would be great if you could test this patch (through some >> reboots) and report back. >> >> Then, I don't think it's an issue with the device. >> There is a long run TODO (mentioned in the header of libshut.c) >> that...

Hello, I forgot nut since more than a year because a lot of job with other application My server nut failed since severals months We had 3 electric failure so I must install a new server nut I work with ubuntu 10.04.4 (64bits) / I installed nut 2.4.3 with deposits I have a MGE Pulsar evolution 2200 connected on usb last week when I began my tests all was ok (communication etc etc ..)